diff options
| author | Chris Evich <cevich@redhat.com> | 2022-08-05 11:02:20 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2022-08-09 11:22:15 -0400 |
| commit | d2d7898b8a829ffd4638ba0243affd14c66eb05c (patch) | |
| tree | f2f8faff4949b17431171e24c17b0816f05ac73b /vendor/github.com/pkg/sftp/attrs.go | |
| parent | 097cc6eb6dd8e598c0e8676d21267b4edb11e144 (diff) | |
| download | podman-d2d7898b8a829ffd4638ba0243affd14c66eb05c.tar.gz podman-d2d7898b8a829ffd4638ba0243affd14c66eb05c.tar.bz2 podman-d2d7898b8a829ffd4638ba0243affd14c66eb05c.zip | |
Cirrus: Improve CI VM image updates for EC2
AWS EC2 keys VM images by an utterly unreadable, horrible to use,
generated "AMI ID" value. This is very error prone for humans in
practice, since it's impossible to tell one image from the next by
eye. Worse, EC2 permits duplicate name-tag values, complicating
image specification further.
However fortunately, Cirrus-CI recently implemented a feature by
which AMI's may be referenced by a name-tag search - choosing
the most recent AMI found. Since the `containers/automation_images`
build workflow always assigns a unique name + `$IMAGE_SUFFIX` value,
we can simply re-use it for both AWS and GCP image specification.
In other words as of this commit, specifying new CI VM images can
be done by simply updating the `$IMAGE_SUFFIX` value as we've always
done. No need to call out a specific AMI ID just for EC2 tasks.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'vendor/github.com/pkg/sftp/attrs.go')
0 files changed, 0 insertions, 0 deletions