Skip to content

Feature: mark variables/fields as private so they don't get added to logs/history #2887

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

Open
northwestnodes-eric opened this issue Apr 8, 2025 · 4 comments
Labels

Comments

@northwestnodes-eric
Copy link

Related to

Ansible (task execution)

Impact

security improvements

Missing Feature

We would like to have an option for a variable field to be marked as private/secret such that the value is not stored in the history.

Implementation

Add a variable to a task template.
Have a checkbox that says "Private" or something along those lines.
Make sure the Private marked variable does not get stored in the run history/logs.

Design

No response

@kris9854
Copy link

Cool feature but why not just use ansible-vault on a playbook level?

@northwestnodes-eric
Copy link
Author

Because of our security policies that state that sensitive information can only be stored in a single designated location at-rest, and that so happens to not be an arbitrary secrets.yml file on a command and control server.

Or,

Why build a tool like SemaphoreUI and then leave out half the features that would make this tool more secure to use?

@fiftin
Copy link
Collaborator

fiftin commented Apr 20, 2025

@northwestnodes-eric What variable do you mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants