(feat): Add fallback non-assigned block device mapping #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ebs-bootstrap
should not fail if an Instance Store volume with an unassigned block device mapping is attached to the EC2 Instance. Especially if this Instance Store volume is not mentioned in the configuration file. Therefore, I have added a fallback clause where in if the Vendor Specific information fails to expose a block device mapping, it will now fallback to a safer option, rather than erroring out.I've also updated the testing frame work to remove the need to explicitly mention what Vendor Specific Padding to use in the NVMe test cases