-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle colon-delimited environmentpath in config_version.sh #64
base: production
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a typo here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed!
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.conf
passes the Puppet configuration value$environmentpath
as 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
.