-
Notifications
You must be signed in to change notification settings - Fork 318
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: add support for role based auth flag #2519
Conversation
c2a94c0
to
34411ab
Compare
Currently we are not able to delete already stored secrets from Config BE DB so we are adding support role based auth flag so that users can easily switch between AWS Access Keys and Roles.
34411ab
to
91f425d
Compare
Codecov ReportBase: 45.36% // Head: 45.35% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2519 +/- ##
==========================================
- Coverage 45.36% 45.35% -0.01%
==========================================
Files 175 175
Lines 36377 36387 +10
==========================================
+ Hits 16502 16503 +1
- Misses 18799 18808 +9
Partials 1076 1076
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Tested on dev cluster and changes are working as expected. |
Description
Currently we are not able to delete already stored secrets from Config BE DB so we are adding for support roleBasedAuth flag so that users can easily switch between AWS Access Keys and Roles. This enables to revert back to Access keys if users are getting any troubles after migrating to the AWS roles.
Notion Ticket
https://www.notion.so/AWS-FTR-Support-RoleBasedAuth-Flag-5cfd191922ae4f6eb4a8fc75dca40ac3
Security