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

Secret env variables #161

Open
wrdls opened this issue Feb 8, 2019 · 3 comments
Open

Secret env variables #161

wrdls opened this issue Feb 8, 2019 · 3 comments

Comments

@wrdls
Copy link

wrdls commented Feb 8, 2019

Hi,

I'd like support for secret variables. By this I mean that the value isn't shown when you run envman print.
Use case for this is to print the env in a CI pipeline so it's easier to see why your build is failing but I'd like to hide credentials from developers.

This commit seems to add support for what I'm asking but I'm not sure what is does. I tried to set this field but the value was still printed:

envs:
  - SECRET: password
    opts:
      is_sensitive: true

Workaround could be to use something like envman print | grep -v SECRET_VAR but a native solution would be nice.

@fehersanyi-bitrise
Copy link

Hello there!

are you trying to set this up locally?
if the secret is set up properly, in the logs it should write [REDACTED] instead of the value
on secrets you can read more on our devcenter: https://devcenter.bitrise.io/bitrise-cli/secrets/

@wrdls
Copy link
Author

wrdls commented Feb 11, 2019

I don't use bitrise but found this tool while searching for something to manage environment variables.

So yes, I'm running this locally as well as in a CI pipeline.

@fehersanyi-bitrise
Copy link

in yml firmat, we use a different file called secrets.bitrise.yml to hold these values, I guess the cli can't handle it if you define this way 🤔

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

No branches or pull requests

2 participants