WHAT

Provide design explorations that show how the billing account selection can be included in the Create Kafka instance modal, and how it affects messaging and other options in the creation form.

Designs should also show how this property can display after creation. Assumption is that we would have a separate property to display with the Kafka instance details:

• hyperscaler marketplace
• hyperscaler account id

WHY

With the option to purchase RHOSAK through AWS marketplace, there's a potential that the same RH org would have multiple accounts set up with AWS. If the user wants to provision an instance using an AWS account, they need to be able to select which account to use. 

HOW

• Draft designs that illustrate options available for including the account select option in the form
• Designs should illustrate how the rest of the form changes based on the new select menu and based on the option selected.
• Design variations should address the following scenarios:
  • A user has only one account with one marketplace set up, either RH marketplace, AWS or Azure.
  • A user has many accounts with one marketplace set up, either AWS or Azure.
  • A user has many accounts with many marketplaces set up.  
• Design variations should address the following criteria: 
  • When the user selects an account with a specific hyperscaler / cloud provider, then the user should not see an option to select a different cloud provider for the "Cloud provider" option. For example, I cannot choose an AWS account for billing and then be able to select Azure as the cloud provider option. 
  • Other job stories created as Jira stories in the epic MGDSTRM-6923 should be considered as acceptance criteria. 

DONE

• Designs are shared with stakeholders and iterated upon until a final design direction is provided.
• Any open design or microcopy requirements that emerge from the design and review process that haven't been finalized for this task are captured as new design tasks.