There are situations in which infra-admins could use run-books for quicker troubleshooting issues affecting prod infrastructure or services.
Ofc, a scenario like "getting DB access/credentials to execute a query in service-xyz" should be avoided as much as possible, but when there is no way around it, having a run-book in-place -- ideally in sync with decisions encoded as IaC -- would be great to save time.
This might also extends for other stuff we have, like simple migration instructions we have to follow as admins. Github branch renaming or enabling trusted publishing are two examples of of instructions we already have, but as of now they are not centralized and one might need to recollect where to find them.
If this looks reasonable, we could decide whether these run-books would be public, perhaps using this repo to host them in this case.
There are situations in which infra-admins could use run-books for quicker troubleshooting issues affecting prod infrastructure or services.
Ofc, a scenario like "getting DB access/credentials to execute a query in
service-xyz" should be avoided as much as possible, but when there is no way around it, having a run-book in-place -- ideally in sync with decisions encoded as IaC -- would be great to save time.This might also extends for other stuff we have, like simple migration instructions we have to follow as admins. Github branch renaming or enabling trusted publishing are two examples of of instructions we already have, but as of now they are not centralized and one might need to recollect where to find them.
If this looks reasonable, we could decide whether these run-books would be public, perhaps using this repo to host them in this case.