You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Volume tagging can be set in cloud map as implemented in this change: #18451
However, tagging of root volume in the cloud map is not possible.
I have tried a couple of different tests.
duplicate the block_device_mappings volume config in the volumes: {} block. This creates two volumes and fails to attach one.
add tagging directly to the block_device_mappings block, no success here either.
In our automation we have to get return metadata from AWS, do an instance/root vol lookup and then add a tag. This is a lot of extra code to workaround.
The text was updated successfully, but these errors were encountered:
gtmanfred
added
the
Feature
new functionality including changes to functionality and code refactors, etc.
label
Apr 16, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
Volume tagging can be set in cloud map as implemented in this change: #18451
However, tagging of root volume in the cloud map is not possible.
I have tried a couple of different tests.
In our automation we have to get return metadata from AWS, do an instance/root vol lookup and then add a tag. This is a lot of extra code to workaround.
The text was updated successfully, but these errors were encountered: