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.

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

Blueprint history: make encrypted keys unrecognisable in the blueprint CR #38

Closed
meiserloh opened this issue Feb 19, 2024 · 0 comments · Fixed by #56
Closed

Blueprint history: make encrypted keys unrecognisable in the blueprint CR #38

meiserloh opened this issue Feb 19, 2024 · 0 comments · Fixed by #56

Comments

@meiserloh
Copy link
Contributor

  • Passwords are not visible in plain text
  • If there are errors in the execution, the encrypted keys must be blackened in any case
meiserloh added a commit that referenced this issue Feb 20, 2024
@meiserloh
#38 - censor sensitve configuration data
f9dba13 
The configuration data has to be censored in the blueprint CR to be not visible for anyone after the application or failure.
meiserloh added a commit that referenced this issue Feb 20, 2024
@meiserloh
#38 - tests for sensitve data consoring
7914a1b
meiserloh added a commit that referenced this issue Feb 21, 2024
@meiserloh
#38 - remove pointer receiver and add docs
5c6aba7
meiserloh added a commit that referenced this issue Feb 28, 2024
@meiserloh
#38 - Change code to fit to new config structure
21ecfa1
meiserloh added a commit that referenced this issue Feb 28, 2024
@meiserloh
#38 - add descriptions to crd
56d3166
@meiserloh meiserloh mentioned this issue Feb 28, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/38 make encrypted keys unrecognisable cloudogu/k8s-blueprint-operator
1 participant
@meiserloh