When an environment is deployed in a completely stateless way (no database, no persistent volumes) the schedule for backups is still created.
This can lead to unexpected issues when the purge and check jobs run for these environments, they will fail if there is no associated restic repository, as this is only created when the first backups are performed.
The build-deploy-tool should check if there are any components that required backups, and if so, only then create the schedule.
When an environment is deployed in a completely stateless way (no database, no persistent volumes) the schedule for backups is still created.
This can lead to unexpected issues when the purge and check jobs run for these environments, they will fail if there is no associated restic repository, as this is only created when the first backups are performed.
The build-deploy-tool should check if there are any components that required backups, and if so, only then create the schedule.