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

Add option to ignore sensitive info while parsing nginx configs #229

Closed
nkashiv opened this issue Feb 28, 2023 · 1 comment · Fixed by #343
Closed

Add option to ignore sensitive info while parsing nginx configs #229

nkashiv opened this issue Feb 28, 2023 · 1 comment · Fixed by #343
Labels
enhancement New feature or request

Comments

@nkashiv
Copy link
Contributor

nkashiv commented Feb 28, 2023

Currently the agent uploads all the Nginx config files that are in the config_dirs path.

However a user may not be comfortable with sending their Nginx configs incase it contains sensitive information they want to protect.

The proposed enhancement is to add an option to sanitize the contents of the Configs using Crossplane's Ignore Directives like:

  • 'ssl_certificate_key'
  • 'ssl_client_certificate'
  • 'ssl_password_file'
  • 'ssl_stapling_file'
  • 'ssl_trusted_certificate'
  • 'auth_basic_user_file'
  • 'secure_link_secret'
    Before uploading them to the controller.
@nkashiv nkashiv added the enhancement New feature or request label Feb 28, 2023
@mtbChef
Copy link
Contributor

mtbChef commented Mar 7, 2023

Thanks @nkashiv! We've added this enhancement to the backlog and will evaluate it for roadmap fit

u5surf added a commit to u5surf/agent that referenced this issue Jun 11, 2023
@u5surf u5surf mentioned this issue Jun 11, 2023
6 tasks
u5surf added a commit to u5surf/agent that referenced this issue Jun 12, 2023
* for all crossplane.ParseOptions
u5surf added a commit to u5surf/agent that referenced this issue Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants