"Add Account" modal part 2: Role
As a cloudigrade user, I want to see instructions for setting up my AWS Role when I step through the "Add Account" modal so that I know how to proceed with creating my AWS Role.
Acceptance Criteria
-
Verify that this new screen is show when the user clicks "Next" on the "Policy" step of the "Add Account" modal. -
Verify the screen has visual elements and text that look like the design wireframes. -
Verify there is a read-only text area containing cloudigrade's AWS Account ID. -
Verify that clicking the "Copy" button copies cloudigrade's AWS Account ID to the clipboard. -
Verify that clicking "Cancel" closes the modal and returns the user to the "Welcome" screen. -
Verify that clicking "Back" shows the previous "Policy" screen. -
Verify that clicking "Next" replaces the modal contents. - The replacement content may just be placeholder text. Functional contents will come later!
-
Verify that clicking "Back" from the next placeholder view returns the user to this Role screen. -
Verify that a retrieve-only ( HTTP GET
) API exists at/api/v1/sysconfig/
that includes the cloudigrade AWS Account Id that we want the customer to use when configuring her AWS Role.
Assumptions and Questions
- Design is based on https://redhat.invisionapp.com/share/UFI078IZVAW
-
Do we want the AWS Account ID to live as static content in frontigrade? Or should frontigrade ask the cloudigrade API for this value? The latter is more complex but means we don't have to update frontigrade if/when we change the AWS Account ID (which will vary depending on environment).- We discussed this question, and this value should come from the API somewhere.
-
HTTP GET /api/v1/sysconfig/
should return an object like:{ "aws_account_id": 1234567890 }
- TBD: How do we feel about that URL?
- The object is very simple now, but it may grow to include more values (like an Azure account ID) in the future. Maybe in the future it'll look like:
{ "aws_account_id": 1234567890, "azure_account_id": 1234567890, "gcp_account_id": 1234567890 }
- TBD: Is there anything else clever we should put in this design to help future-proof ourselves?
-
- We discussed this question, and this value should come from the API somewhere.