adds playbook to switch a production instance to use the staging apt repo #5452
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
…epo for testing purposes (Playbook formerly available at https://gist.githubusercontent.com/conorsch/e7556624df59b2a0f8b81f7c0c4f9b7d/raw/294294cc4fb243569e121d93350fdee2b2e0920d/securedrop-qa.yml)
zenmonkeykstop
requested review from
conorsch,
emkll and
kushaldas
as code owners
zenmonkeykstop
changed the title
rmol
approved these changes
Aug 19, 2020
There was a problem hiding this comment.
👍
- set up a production instance (VMs or HW) using the current release version.
- check out this branch
- follow the instructions in
~/Persistent/securedrop/install_files/ansible-base/securedrop-qa.ymlto run the playbook - log on to
appandmonand verify that- the testing apt key has been added, with the command
sudo apt-key list 2211B03C - the files
/etc/apt/security.listand/etc/apt/sources.list.d/apt_freedom_press.listreference apt-test.freedom.press, not apt.freedom.press - the command
apt-cache policy securedrop-keyringincludes apt-test.freedom.press versions in the version table
- the testing apt key has been added, with the command
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.
Status
Ready for review
Description of Changes
Towards #3792 .
Updates and adds the playbook formerly available at https://gist.githubusercontent.com/conorsch/e7556624df59b2a0f8b81f7c0c4f9b7d/raw/294294cc4fb243569e121d93350fdee2b2e0920d/securedrop-qa.yml, allowing devs and testers to test the upgrade scenario with release candidate versions..
Testing
~/Persistent/securedrop/install_files/ansible-base/securedrop-qa.ymlto run the playbookappandmonand verify thatsudo apt-key list 2211B03C/etc/apt/security.listand/etc/apt/sources.list.d/apt_freedom_press.listreference apt-test.freedom.press, not apt.freedom.pressapt-cache policy securedrop-keyringincludes apt-test.freedom.press versions in the version tableDeployment
No special requirements