-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bump Ubuntu Focal #24
Conversation
CHANGELOG.md
Outdated
- Add `CanonicalAmiProvider.Builder.avoidUnattendedUpgrades` for bumping `imageName` to Focal or higher. | ||
|
||
### Fixed | ||
- Unpin Ubuntu Focal version in `CanonicalAmiProvider.Builder` by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Controversial, because it goes against repeatable builds (our Robustness value).
OTOH our first value is Meaningfulness and I bet our users do update their Ubuntus all the time (no evidence for the claim tho).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could rethink the approach if the less-repeatable builds around Ubuntu build would ever bite us. If we can easily switch back to the fixed build I think we are good to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nvm, see 519dcf1
CHANGELOG.md
Outdated
|
||
### Fixed | ||
- Unpin Ubuntu Focal version in `CanonicalAmiProvider.Builder` by default. | ||
You can still pin a specific release date, e.g. `imageName("ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20240531")` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
This reverts commit b5a272e. The DescribeRequest via Java SDK the filter didn't work like "contains", but as "equals". Weird, because via GUI it always works like "contains". And on HTTP level the requests look almost identical (hostname is different). Anyway, we're back to a pinned (and bumped) version.
No description provided.