Upgrade to Debian Bullseye (AKA Debian 11) #83
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsf9k
added
blocked
dav3r
reviewed
Sep 12, 2021
jsf9k
force-pushed
the
improvement/use-bullseye
branch
from
928b8e1 to
f6edab0
Compare
jsf9k
added
the
hacktoberfest-accepted
mcdonnnj
force-pushed
the
improvement/use-bullseye
branch
from
ea07b11 to
39c7666
Compare
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🗣 Description
This pull request upgrades the
packerconfiguration to use a Debian Bullseye base image. Previously it was using a Debian Buster base image.I also took the liberty of subscribing both our staging and production COOL Images accounts to the official Debian 11 AMI, which is the base AMI referenced in this repo's
packerconfiguration.💭 Motivation and context
Debian Bullseye has been out for almost a month, and the Debian Buster packages are getting pretty long in the tooth, so it makes sense to upgrade all our AMIs.
This will also encourage us to check it there is an updated base AMI for each of our AMIs that are built on something other than Debian.
Once these changes are propagated down, they will resolve cisagov/assessor-workbench-packer#2 and also resolve cisagov/pca-gophish-composition-packer#56.
🧪 Testing
All
pre-commithooks and GH Actions checks pass.✅ Checklist