This version is to resolve a handful of exceptions that are occurring in order to resolve those errors as well as help to make it easier to understand what is wrong with the current import process here.
Apply any post-deployment configuration changes (see section Configuration Changes)
Post-deployment checks (is the web service responding, can you refresh the data using the HaikuDepot app)
Commit and push the updated deployment configuration to GitHub.
Announce the update on the haiku-sysadmin and haiku mailing list.
Configuration Changes
Please list any configuration changes, and note whether they need to be done pre-deploy or post-deploy
None
Rollback Plan
If the update is unsuccessful, the rollback can be executed as follows.
If there has been a (failed) database migration as part of the change, the backup created in step 2 must be restored. If the database has not been affected, then skip to the image rollback steps below.
Description
Update HaikuDepot to version 1.0.163
This version is to resolve a handful of exceptions that are occurring in order to resolve those errors as well as help to make it easier to understand what is wrong with the current import process here.
How has the change been tested
Steps to implement the change
Note: Please mark changes from the default steps below in bold
deployments/haikudepotserver.yml
.haiku-sysadmin
andhaiku
mailing list.Configuration Changes
Please list any configuration changes, and note whether they need to be done pre-deploy or post-deploy
None
Rollback Plan
If the update is unsuccessful, the rollback can be executed as follows.
If there has been a (failed) database migration as part of the change, the backup created in step 2 must be restored. If the database has not been affected, then skip to the image rollback steps below.
deployments/other/restore-pg.yml
by making sure the container args point to the haikudepotserver container