Support alternate Forge for 'bolt module' workflow #2303
Assignees
Labels
Feature
New features and improvements.
Comments
9 tasks
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 6, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 6, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 6, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 10, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 10, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 11, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
It would be even more valuable to support git repos (and refs) for individual modules in these environments (as the older |
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Nov 16, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
…modules This adds support for specifying an alternate Forge and proxies when installing modules using the `bolt module add|install` and `Add|Install-BoltModule` commands. This change includes upstream changes to the `puppetfile-resolver` library and a new config option in Bolt. The new `module-install` config option accepts a map that configures an alternate Forge and proxies to use when resolving and installing modules. This option is identical to the current `puppetfile` config option, and is only used when running the `bolt module add|install` and `Add|Install-BoltModule` commands. This setting is available to both the project config file, `bolt-project.yaml`, and the defaults config file, `bolt-defaults.yaml`. It is not available to the `bolt.yaml` config file. This option is passed to the module installer, which in turn passes it to both `puppetfile-resolver` and `r10k` when resolving and installing modules, respectively. !feature * **Support alternate Forge and proxies when installing modules** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports specifying an alternate Forge and proxies to use when installing modules using the `bolt module add|install` commands and `Add|Install-BoltModule` cmdlets. An alternate Forge and proxies can be configured using the new `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`.
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
This adds a new `module-install` config option that is meant to replace `puppetfile`. The config option accepts the same sub-options as `puppetfile` does. Currently, this config option is not respected when resolving module dependencies, as changes need to be made to the `puppetfile-resolver` library to support proxies and an alternate Forge. However, this config is still passed to r10k, which will respect it when installing modules from a Puppetfile. If a user has `module-install` configured and then runs `bolt module add|install` or `Add|Install-BoltModule`, Bolt will issue a warning letting the user know that the config option will not be respected when resolving modules, and then provides a link to a known issue with more information. This also adds a handful of warnings that are issued depending on whether `puppetfile` or `module-install` are configured and if the user runs `puppetfile install` or `module install`. If both options are configured, Bolt will also warn and use `module-install`. This also updates the project migrator to update the `puppetfile` option to `module-install`. !feature * **Add `module-install` configuration option** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports a `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`. This option is used to configure proxies and an alternate forge when installing modules using the `bolt module add|install` commands or `Add|Install-BoltModule` cmdlets. _This option is not currently supported when resolving module dependencies._
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 4, 2020
This adds a new `module-install` config option that is meant to replace `puppetfile`. The config option accepts the same sub-options as `puppetfile` does. Currently, this config option is not respected when resolving module dependencies, as changes need to be made to the `puppetfile-resolver` library to support proxies and an alternate Forge. However, this config is still passed to r10k, which will respect it when installing modules from a Puppetfile. If a user has `module-install` configured and then runs `bolt module add|install` or `Add|Install-BoltModule`, Bolt will issue a warning letting the user know that the config option will not be respected when resolving modules, and then provides a link to a known issue with more information. This also adds a handful of warnings that are issued depending on whether `puppetfile` or `module-install` are configured and if the user runs `puppetfile install` or `module install`. If both options are configured, Bolt will also warn and use `module-install`. This also updates the project migrator to update the `puppetfile` option to `module-install`. !feature * **Add `module-install` configuration option** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports a `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`. This option is used to configure proxies and an alternate forge when installing modules using the `bolt module add|install` commands or `Add|Install-BoltModule` cmdlets. _This option is not currently supported when resolving module dependencies._
beechtom
added a commit
to beechtom/bolt
that referenced
this issue
Dec 7, 2020
This adds a new `module-install` config option that is meant to replace `puppetfile`. The config option accepts the same sub-options as `puppetfile` does. Currently, this config option is not respected when resolving module dependencies, as changes need to be made to the `puppetfile-resolver` library to support proxies and an alternate Forge. However, this config is still passed to r10k, which will respect it when installing modules from a Puppetfile. If a user has `module-install` configured and then runs `bolt module add|install` or `Add|Install-BoltModule`, Bolt will issue a warning letting the user know that the config option will not be respected when resolving modules, and then provides a link to a known issue with more information. This also adds a handful of warnings that are issued depending on whether `puppetfile` or `module-install` are configured and if the user runs `puppetfile install` or `module install`. If both options are configured, Bolt will also warn and use `module-install`. This also updates the project migrator to update the `puppetfile` option to `module-install`. !feature * **Add `module-install` configuration option** ([puppetlabs#2303](puppetlabs#2303)) Bolt now supports a `module-install` configuration option in `bolt-project.yaml` and `bolt-defaults.yaml`. This option is used to configure proxies and an alternate forge when installing modules using the `bolt module add|install` commands or `Add|Install-BoltModule` cmdlets. _This option is not currently supported when resolving module dependencies._
Use Case
There is currently no way of specifying an alternate Forge URL when using the new
bolt moduleworkflow for managing module dependencies. This is supported in the olderbolt puppetfileworkflow, and something that is almost a necessity in a corporate environment where Bolt plans may rely on internal modules that cannot be published to the Puppet Forge.We should make a new setting with the exact same structure and keys as
puppetfileconfig option. It's calledmodule-install.We should also update bolt project migrate to update this setting to update
puppetfiletomodule-install.If you have the (
modulesormodule-install) key and thepuppetfilekey you will get a warning to update thepuppetfilekey tomodule-installwithbolt project migrate. It will not honor the puppetfile key.module-installshould not be honored bypuppetfilesubcommands.The text was updated successfully, but these errors were encountered: