(GH-2022) Pickup puppet agent 4.1.1 #2110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CLA signed by all contributors. |
Puppet agent 4.1.1 includes several updates we'd like to pick up, including: - Stopping agent runs if Puppet is upgraded mid-run - Adding a puppet_agent::run plan to run the agent on remote targets This allows users to run the agent without Bolt erroring due to a non-zero exit code. This additionally fixes up a Windows test that upgrades the agent. The puppet_agent module will now error when attempting to upgrade on Windows while the service is running, so we now stop the service before upgrading. Closes puppetlabs#2022 !feature * **Add puppet_agent::run plan to run the agent** ([puppetlabs#2022](puppetlabs#2022) The puppet_agent::run plan will run the agent if it's available and returns a resultset including agents that failed and the results from runs that succeeded.
beechtom
approved these changes
Aug 25, 2020
beechtom
added a commit
to beechtom/bolt
that referenced
this pull request
Sep 24, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
beechtom
added a commit
to beechtom/bolt
that referenced
this pull request
Sep 28, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
beechtom
added a commit
to beechtom/bolt
that referenced
this pull request
Nov 10, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
beechtom
added a commit
to beechtom/bolt
that referenced
this pull request
Nov 10, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
beechtom
added a commit
to beechtom/bolt
that referenced
this pull request
Nov 11, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
dontlaugh
pushed a commit
to dontlaugh/bolt
that referenced
this pull request
Dec 18, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
dontlaugh
pushed a commit
to dontlaugh/bolt
that referenced
this pull request
Dec 18, 2020
This updates the `bolt project init` command to configure `modules` in `bolt-project.yaml`, allowing users with new projects to immediately start using the module workflow. - If `bolt project init` is run, `modules` will be an empty array `[]` - If `bolt project init --modules` is run, `modules` will be an array of declarations for the specified modules This also updates the command so that it can only be run once per project. Previously, if a project had a configuration file, but no `Puppetfile`, the `bolt project init --modules` command would still install modules. Now, Bolt will error in this case and display a helpful error that the user should instead use the `bolt module add` command. !feature * **Configure `modules` with `bolt project init`** ([puppetlabs#2110](puppetlabs#2210)) The `bolt project init` command will now configure the `modules` key in the `bolt-project.yaml` file, enabling the `bolt module` command.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Puppet agent 4.1.1 includes several updates we'd like to pick up,
including:
This allows users to run the agent without Bolt erroring due to a
non-zero exit code.
Closes #2022
!feature
Add puppet_agent::run plan to run the agent (#2022
The puppet_agent::run plan will run the agent if it's available and
returns a resultset including agents that failed and the results from
runs that succeeded.