Skip to content
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

Allow S3 Fetch config with dashes in the name to still work #17

Merged
merged 1 commit into from
Dec 11, 2015
Merged

Allow S3 Fetch config with dashes in the name to still work #17

merged 1 commit into from
Dec 11, 2015

Conversation

DennisDenuto
Copy link
Contributor

When a S3 Fetch config repo or package name contains a dash in the name, the material environment variables (GO_PACKAGE_*) are saved as an underscore (bash restriction). This can lead to confusion when the fetch configs 'appear' correct however the S3 Fetch plugin complains about the configuration.

@@ -15,6 +15,7 @@

import static com.indix.gocd.utils.Constants.*;
import static org.hamcrest.Matchers.is;
import static org.hamcrest.Matchers.nullValue;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove this if we're not using it? :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops! done :-)

@ashwanthkumar
Copy link
Member

LGTM.

cc: @manojlds @Sriram-R

@manojlds
Copy link
Member

LGTM - #8

manojlds added a commit that referenced this pull request Dec 11, 2015
Allow S3 Fetch config with dashes in the name to still work
@manojlds manojlds merged commit b2a627e into indix:master Dec 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants