Closed owenfarrell closed 1 year ago
Kudos, SonarCloud Quality Gate passed!
In stewing on this a bit more, I took a crack at what an "auto-upgrade" approach looks like as part of #203. The idea is that it reverse engineers the random suffix that was generated based on existing result(s) using a guess-and-check approach.
Closing as superseded by #203
Signed-off-by: Owen Farrell owen.farrell@gmail.com
Fixes #140
PR Checklist
resourceDefinition.json
models_generated.go
file in my PR)Description
Does this introduce a breaking change
While this doesn't inherently introduce a backwards-breaking change, I don't see a way to support auto-upgrades of the current version of the provider to support this change. Anyone who attempts to auto-upgrade will incur the existing behavior (a forced deletion/recreation of downstream resources) one more time. Any suggestions on how to mitigate this issue would be appreciated.
Testing
In addition to local unit testing, I've exercised these updates via a local provider override and it seems to meet the need.