🌱 Install capi-operator as a turtles dependency in a dev-env #869
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Improves dev environment setup for turtles, making it use actual turtles chart capi-operator as a dependency, as opposed to installing upstream one separately.
This allows to rely on
CAPIProvider
versions when deploying providers, so incompatibility in providers matrix is eliminated based on centralization of the providers version management.Additionally this makes dev-env adhere to supported configuration described in turtles docs (more closely), and improves development process for etcd snapshot restore and other features.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist: