-
Notifications
You must be signed in to change notification settings - Fork 87
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
[FEATURE]: Create/Amend mapping between storage prefixes and cloud principals #910
Closed
1 of 5 tasks
Tracked by
#333
Labels
cloud/aws
Issues related to AWS
cloud/azure
issues related to Azure
feat/cli
CLI commands
migrate/access-control
Access Control to things
Comments
FastLee
added
enhancement
New feature or request
cloud/azure
issues related to Azure
needs-triage
credentials
cloud/aws
Issues related to AWS
labels
Feb 7, 2024
1 task
1 task
nfx
added
feat/cli
CLI commands
and removed
enhancement
New feature or request
needs-triage
labels
Mar 25, 2024
@FastLee create end-to-end user flow for principal creation in both azure and aws. with screenshots. |
nfx
added
migrate/access-control
Access Control to things
and removed
credentials
labels
Apr 22, 2024
@FastLee when it's going to be done? |
22 tasks
@FastLee this is high-prio :) |
Closed by #1495 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cloud/aws
Issues related to AWS
cloud/azure
issues related to Azure
feat/cli
CLI commands
migrate/access-control
Access Control to things
Is there an existing issue for this?
Problem statement
In the process of creating storage credentials we have to map storage credentials to intended cloud principals so we can create these principals.
Proposed Solution
The mapping will detect the existing storage credentials and will surface the missing principal/roles that needs to be created for the missing storage credntials.
We should allow the user to select between few options of mapping:
The principal can be an AWS Role an Azure SPN or an Azure MI
The process will generate a mapping CSV and upload it to the workspace.
The mapping document will have the following format:
Checklist
The text was updated successfully, but these errors were encountered: