Salvatore
Salvatore
Hi. I'm trying to setup backups on S3 for a PostgreSQL database, but I can't understand how to schedule them using the helm chart. In [line 300](https://github.com/percona/percona-helm-charts/blob/main/charts/pg-db/templates/cluster.yaml#L300) I can see...
Both when no changes are detected by the plan and when the message is correctly sent to slack following a change detection, in the action logs I receive this error:...
In the plan steps I have also infracost, so when the drift-detection action runs, also the infracost APIs are called, even if it’s useless for this job. Is it possible...
The message sent to slack has not enough information from my point of view. For example: `Drift detected in digger project prd details below: ` It’s much better to have...
Even if https://github.com/diggerhq/digger/pull/1290 solved the issue of the execution of custom workflows with orchestrator, in the action logs the name of the workflow executed is empty: `Running 'digger plan' for...
 With digger v0.4.34 there is a bug when the backend is used in the drift detection action. The problem is not present if `no-backend: true` is set