We currently enforce Launch users to always enter all the details even when they use Launch Template. That includes:

• Instance Type
• Public key

Both fields can be set in templates (both AWS and GCP), however, some fields can be missing in the template.

We want to be user friendly and in case a template is selected which contains information (type, key or both), the particular UI element should be disabled or allow omitting them and user should be informed that this is set in selected launch template.

What needs to be done as part of this epic:

• New endpoint that fetches detail of a template and returns only relevant fields (type, key)
• UI changes which will utilize the new endpoint to disable/enable elements on the page
• Change of the reservation API input (key, type) from required to optional for both AWS and GCP
• UX confirmation of the UI solution
• Document OpenAPI spec on the new behavior
• Documentation update
• We should think of metrics for this feature
  • first idea is to track what template was used and what fields were applied from the template

Resources:

• AWS docs for DescribeLaunchTemplateVersion
• Sum up from slack conversation on the topic: https://docs.google.com/document/d/1AMUTM6pLRymueFJPdTMNDkIAwwX3N_VBp13GFuEGN0E/edit