Handle colon-delimited environmentpath in config_version.sh#64
Handle colon-delimited environmentpath in config_version.sh#64mbaynton wants to merge 1 commit intopuppetlabs:productionfrom
Conversation
|
@mbaynton Can you share an example of the script bombing out? |
scripts/config_version.sh
Outdated
| @@ -1,12 +1,22 @@ | |||
| #!/bin/bash | |||
| if [ -e $1/$2/.r10k-deploy.json ] | |||
| RONMENTPATH=$1 | |||
There was a problem hiding this comment.
Looks like a typo here.
|
After modifying the compile master's |
|
Apologies this as taken so long to get to @mbaynton can you rebase the pull request please and if it's still required i'll merge it in. |
|
Rebased and merged @abuxton |
|
I just ran into a similar situation where a It works 👍 Though I do have a minor style nitpick about using upper case variables for things that aren't environment variables. |
|
|
environment.confpasses the Puppet configuration value$environmentpathas an argument toconfig_version.sh. This value supports a colon-separated list of paths, but when one is used the config_version scripts currently bomb out.This fixes them to handle colon-delimited
environmentpath.