Allow manage objects with scope Namespaced #314
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: vaspahomov <vas2142553@gmail.com>
|
I don't think we're likely to support this without a major version bump per my comment at crossplane/crossplane#2255. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: vaspahomov vas2142553@gmail.com
Description of your changes
Added support of Namespaced Managed Resources. In my mind this patch will not affect on current behaviour with Cluster scoped resources. But with this patch you can use Namespaced objects as well as Cluster scoped.
Fixes #251
I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Manually tested with provider-aws, provider-azure with replace in go.mod