Cirrus: Enable labeling of EC2 VMs #18072
Merged
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.
In GCP, user specified VM names are required upon creation. Cirrus-CI generates helpful names containing the task-ID. Unfortunately in EC2 the VM ID's are auto-generated, and special permissions are required to allow secondary setting of a
Name
tag. Since this permission has been granted, enable theexperimental
flag on EC2 tasks so that cirrus can update VM name-tags. This is especially useful in troubleshooting orphaned VMs.Ref:
#18065 (comment)
Does this PR introduce a user-facing change?