I reverted today's deployment of envvars-api 0.0.50 because that depends on envvars-cli commit 3c116128 which hasn't been deployed yet. This was manifesting as "Error: method not allowed" errors when creating new envvars.
Please either immediately deploy the envvars-cli changes and then roll envvars-api forward again, or revert the breaking change to envvars-api and then deploy that revert.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Raymond_Ndibe | T367961 envvars-api 0.0.50 depends on unreleased envvars-cli changes | |||
| Resolved | dcaro | T368516 [envvars-api] version 0.0.50 introduces breaking changes that need adapting for replica_cnf service | |||
| Resolved | dcaro | T368909 [toolforge,replica_cnf] Use tool-prefixed urls for envvars |
Hello @taavi , thanks for helping reverse this. This was a oversight on my path. I thought the cli changes has already been deployed
.. and T368516: [envvars-api] version 0.0.50 introduces breaking changes that need adapting for replica_cnf service needs fixing before we can do that, so marking that as a subtask.