fix: Do not late-initialize exclusive fields in pagerduty_service #19
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: Holger Johannes Heinz <holgerjohannes.heinz@dkb.de>
haarchri
approved these changes
Aug 2, 2023
|
@haarchri Could we get this backported to release-0.5, or otherwise released? |
|
Amazing, thank you! |
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.
Description of your changes
In
services.service.pagerduty.crossplane.iothe fieldsalertGroupingParametersandalertGroupingTimeoutare mutually exclusive. The provider therefore fails to observe the created resource; this PR fixes this by adding these fields toIgnoredFieldsin the config.I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Ran provider and created service object.