Closed mble-sfdc closed 1 month ago
The current list of valid TZs in https://github.com/heroku/cli/blob/v9.0.0/packages/cli/src/commands/pg/backups/schedule.ts#L24-L38 is very limited - only covering UTC-8 to UTC+1
Thank you for reporting, we'll take a look.
A fix for this was released in v9.2.0 of the CLI. I'm going to close this issue now, but if it continues to be a problem please feel free to reopen.
This project is for the Heroku CLI only and issues are reviewed as we are able. If you need more immediate assistance or help with anything not specific to the CLI itself, please use https://help.heroku.com.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
As per https://devcenter.heroku.com/articles/heroku-postgres-backups#set-up-a-backup-schedule, we should be able to pass in an IANA timezone identifier e.g.
On CLI v9, this returns the following:
This is due to the restricted handling in
parseDate
: https://github.com/heroku/cli/blob/v9.0.0/packages/cli/src/commands/pg/backups/schedule.ts#L59-L73In CLI v8, this was more permissive: https://github.com/heroku/cli/blob/v8.10.0/packages/pg-v5/commands/backups/schedule.js#L21C1-L27C2
What is the expected behavior?
A valid IANA timezone identifier or shorthand is valid for passing into
pg:backups:schedule
, as it was in CLI v8.