Skip to content
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

Break out NoDevice property validation (Fixes #1551) #1553

Merged
merged 1 commit into from Jan 7, 2020

Conversation

cwgem
Copy link
Contributor

@cwgem cwgem commented Jan 6, 2020

  • NoDevice is a string for launch template block device mapping and a null object for EC2 block device mapping
  • This addresses the issue by breaking out block device mapping to two separate objects. The EC2 version will keep the original name for backwards compatibility purposes and the launch template version will take up a new name

@cwgem
Copy link
Contributor Author

cwgem commented Jan 6, 2020

Working on fixing the testing issues

* NoDevice is a string for launch template block device mapping and
  a null object for EC2 block device mapping
* This addresses the issue by breaking out block device mapping to
  two separate objects. The EC2 version will keep the original name
  for backwards compatibility purposes and the launch template
  version will take up a new name
@cwgem
Copy link
Contributor Author

cwgem commented Jan 6, 2020

The testing issue have been addressed. The original solution was using a shared dictionary between two classes, but after consideration of the script which auto generations object skeletons I went with the more verbose method which duplicates the shared properties between the two device block mapping objects.

@markpeek markpeek merged commit 9688828 into cloudtools:master Jan 7, 2020
@markpeek
Copy link
Member

markpeek commented Jan 7, 2020

Thanks! Agree with you on implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants