-
Notifications
You must be signed in to change notification settings - Fork 172
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
feat: implement conditional secret management #2517
Conversation
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
…nimplemented Signed-off-by: Faeka Ansari <faeka6@gmail.com>
✅ Deploy Preview for docs-kargo-akuity-io ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
@@ -18,6 +18,9 @@ data: | |||
TLS_CERT_PATH: /etc/kargo/tls.crt | |||
TLS_KEY_PATH: /etc/kargo/tls.key | |||
{{- end }} | |||
{{- if .Values.api.enableSecretManagement }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{{- if .Values.api.enableSecretManagement }} | |
{{- if .Values.api.secretManagement.enabled }} |
maybe? To match .api.oidc.enabled
, .api.adminAccount.enabled
, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
enableSecretManagement
matches the enablePermissiveCORSPolicy
imo; which should be good as long as we have not more than one field to be managed for secret management unlike oidc
and adminAccount
wdyt? @hiddeco
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I now notice there is a .api.rollouts.integrationEnabled
, so I guess we have already lost this game.
I would prefer things to be uniform at some point, but will not let this block you now. So go for whatever you think is best.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make an issue for improving the consistency pre-GA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like a few unit tests that use the credential management endpoints may need an update. Their config needs secret management enabled. |
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2517 +/- ##
==========================================
- Coverage 48.32% 48.26% -0.06%
==========================================
Files 254 254
Lines 18133 18155 +22
==========================================
+ Hits 8762 8763 +1
- Misses 8889 8909 +20
- Partials 482 483 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
@rbreeze any chance we can get you to amend this PR with the bits to hide credential-management functionality when the config endpoint says its not enabled? |
Signed-off-by: Remington Breeze <remington@breeze.software>
Signed-off-by: Kent Rancourt <kent.rancourt@gmail.com>
Added a tiny fix in 92f07be |
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
Thank you @fykaa! This is great! |
And @rbreeze, thanks to you as well! |
Signed-off-by: Faeka Ansari <faeka6@gmail.com>
Fixes: #2214
Key changes include:
Configuration updates:
EnableSecretManagement
flagClusterRole
andConfigMap
to manage secrets based on this flagvalues.yaml
andconfig.go
to incorporate the new settingAPI enhancements:
GetConfig
endpoint to includeSecretManagementEnabled
statusEndpoint adjustments:
connect.CodeUnimplemented
when secret management is disabledcc: @krancour @rbreeze