Description:
Standard update on restaging calling out project-updates in particular. However, looks like we might want to update our other buildpack versions after testing that they're not broken.
Acceptance Criteria:
[ ] Update buildpack versions as possible with minimal/no other code changes
[ ] Testing Checklist has been run and all tests pass
[ ] README is updated, if necessary
Tasks:Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
[ ] Update and restage project-updates
[ ] Investigate if newer nginx buildpack impacts frontend
[ ] Investigate if newer python buildpack impacts backend
[ ] Run Testing Checklist and confirm all tests pass
Notes:
I think our backend is on python v.1.7.x, and 1.8.x is available.
Supporting Documentation:
Hi cloud.gov user,
cloud.gov frequently updates the programming language buildpacks available to
our customers. Buildpack updates include programming language updates and
often include security fixes.
We recently updated the buildpack in use by your application. You should
restage or redeploy your application to take advantage of the update.
A rolling restage operation is the quickest way to upgrade without incurring
downtime. You may still want to leverage your deployment infrastructure to
perform the upgrade if you have compliance requirements for redeployment operations.
You can restage your application by opening the command line and entering
the following commands:
Description: Standard update on restaging calling out project-updates in particular. However, looks like we might want to update our other buildpack versions after testing that they're not broken.
Acceptance Criteria:
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
project-updates
nginx
buildpack impacts frontendpython
buildpack impacts backendNotes:
Supporting Documentation:
Open Questions: