From cf708a7aad070da078e12cabd611a0c8fe3cec91 Mon Sep 17 00:00:00 2001 From: Rudy YAYON Date: Thu, 10 Dec 2015 11:22:22 +0100 Subject: [PATCH] MODULES-2861: run stages limitation added to the documentation --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5ab4275..cfad084 100644 --- a/README.md +++ b/README.md @@ -467,12 +467,14 @@ Manages the GPG keys that Apt uses to authenticate packages. This module is tested and officially supported on Debian 6 and 7 and Ubuntu 10.04, 12.04, and 14.04. Testing on other platforms has been light and cannot be guaranteed. +This module is not designed to be split across [run stages](https://docs.puppetlabs.com/puppet/latest/reference/lang_run_stages.html). + ### Adding new sources or PPAs If you are adding a new source or PPA and trying to install packages from the new source or PPA on the same Puppet run, your `package` resource should depend on `Class['apt::update']`, in addition to depending on the `Apt::Source` or the `Apt::Ppa`. You can also add [collectors](https://docs.puppetlabs.com/puppet/latest/reference/lang_collectors.html) to ensure that all packages happen after `apt::update`, but this can lead to dependency cycles and has implications for [virtual resources](https://docs.puppetlabs.com/puppet/latest/reference/lang_collectors.html#behavior). ~~~puppet -Class['apt::update'] -> Package<| |> +Class['apt::update'] -> Package <| provider == 'apt' |> ~~~ ## Development -- 2.32.3