digger
digger copied to clipboard
Stored plans on GCP not having unique IDs
It appears that stored plans don't have unique IDs (see attached screenshot)
Raised by @fleroux514
If run digger plan , which succeeds and stores the plan file on GCP bucket, than append changes to the PR with errors and the plan now fails, is the original plan file deleted from the bucket?
... that would become another blocker .. since digger apply by mistake would apply that original plan file which is not up to date
More from @fleroux514 :
Don't think having unique IDs is the issue. When digger is in the process of running a plan, it should start by deleting the existing one.. Think that should do it and be a quick fix.
I've been doing a lot of debugging/fixing on my own time lately and would appreciate if you could confirm the issue and fix it before I get to testing the latest release again. Think its a basic issue that would affect anyone, and not something specific for my needs.. Adding the PR number to the planfile name would probably be a good idea also..