Skip to content
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.

Investigate Adding Support for t3 and m5 Instance-Types #25

Open
ferricoxide opened this issue Sep 5, 2018 · 1 comment
Open

Investigate Adding Support for t3 and m5 Instance-Types #25

ferricoxide opened this issue Sep 5, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@ferricoxide
Copy link
Member

Problem Description:

AWS has released new instance types that might better align to some deployment-scopes

Expected Behavior:

Support t3 and m5 instance-types where possible

Actual Behavior:

Does not currently support t3 and m5 instance-types at all

(Optional) Fix recommendation:

Update template logic to allow for t3 and m5 instance-types

@ferricoxide ferricoxide added the enhancement New feature or request label Sep 5, 2018
@ferricoxide
Copy link
Member Author

Borrow the GenFive logic from the already-enabled cfn-jenkins project. Ensure:

  • Presence of content in Conditions{} section.
  • Presence content in Mappings{} section
  • Presence of content in growpart directive's devices list in the UserData section

Note: Sonarqube doesn't currently have an AppVolume option: only need to account for root device.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant