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.

Sign up for GitHub

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

Jump to bottom

Secret support #1

Open

winjer opened this issue Sep 10, 2014 · 1 comment

Contributor

winjer commented Sep 10, 2014

Add secret = True or False flag to file resource and ensure it is honoured
Decide on syntax for the execute command that lets you tell it where secrets are, so they aren't logged
Review the resources so that passwords are not leaked:
- File
- Checkout
- Line

Jc2k added a commit that referenced this issue


          #1 - Make sure File() resource honors sensitive flag

3662d83

Jc2k added a commit that referenced this issue


          #1 - Ensure Line() respects the sensitive flag

8ed6b5f

Jc2k added a commit that referenced this issue


          #1 - Don't show the diff to .hgrc if there are passwords involved

06f4946

Jc2k added a commit that referenced this issue


          #1 - Respect sensitive flag for Patch resources

159829d

Member

Jc2k commented Sep 15, 2014

Getting there with this. Need to:

Figure out syntax for Execute so that command and commands can take passwords.
Update Git backend to not log passwords
Update Svn backend to not log passwords

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment