This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
exclude RoleDefinitionID and RoleDefinitionName from RoleAssignment l… #201
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.
this fixes a similar issue to the one described here #106 and fixed here #107
when creating a RoleAssignment and filling in either roleDefinitionId or roleDefinitionName, the opposite field is automatically filled in and results in the error
i would have opened against main branch, but the roleassignment files are missing there (this one for example https://github.com/crossplane-contrib/provider-jet-azure/blob/release-0.12-preview/apis/authorization/v1alpha1/zz_roleassignment_types.go). hopefully it's ok to open against this branch