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 custom env var prefix for encrypt-file #364

Closed
wants to merge 1 commit into from

Conversation

krallin
Copy link

@krallin krallin commented Feb 9, 2016

Hi there,

This PR adds an option for the user to sert a custom prefix for the generated environment variables in the encrypt-file. Our use case here is to reuse a single .travis.yml file across several repositories, and we'd like to ensure the .travis.yml is identical in all repos (it'll make maintenance easier), without having to do everything manually with travis encrypt.

I might need to update the README.md as well? Let me know.


Commit message follows:

This adds a --prefix option to the encrypt-file command, which lets
users customize the name given to the _iv and _key variables.

This can be useful to ensure the name given to the variables is
predictable and make the .travis.yml file easier to reuse against
repositories.

krallin added a commit to krallin/docker-alpine that referenced this pull request Feb 9, 2016
This depends on travis-ci/travis.rb#364, but we
can also use a fork locally for now
This adds a `--prefix` option to the `encrypt-file` command, which lets
users customize the name given to the _iv and _key variables.

This can be useful to ensure the name given to the variables is
predictable and make the `.travis.yml` file easier to reuse against
repositories.
@krallin krallin force-pushed the custom-encrypt-file-prefix branch from dcee2a0 to cac9020 Compare July 31, 2017 13:58
@BanzaiMan
Copy link
Contributor

I'm really sorry for the long delay, but I have to close this PR, since #env_name now takes an extra argument, to ensure it is unique for each file (see #678). If you are still interested in the feature, do open a new PR.

Again, I apologize for the prolonged silence.

@BanzaiMan BanzaiMan closed this Jun 12, 2020
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.

2 participants