-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Behavior definitions to allow complex Execution properties #1131
Merged
adambarreiro
merged 34 commits into
vmware:main
from
adambarreiro:improve-behavior-invocation
Aug 28, 2024
Merged
Improve Behavior definitions to allow complex Execution properties #1131
adambarreiro
merged 34 commits into
vmware:main
from
adambarreiro:improve-behavior-invocation
Aug 28, 2024
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: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
adambarreiro
changed the title
Improve Behavior invocations
Improve Behavior definitions to allow complex Execution
Oct 11, 2023
adambarreiro
changed the title
Improve Behavior definitions to allow complex Execution
Improve Behavior definitions to allow complex Execution properties
Oct 11, 2023
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Signed-off-by: abarreiro <abarreiro@vmware.com>
Didainius
approved these changes
Aug 9, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests pass on 10.6 and 10.4
Signed-off-by: abarreiro <abarreiro@vmware.com>
lvirbalas
reviewed
Aug 16, 2024
lvirbalas
approved these changes
Aug 28, 2024
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.
Problem
With v3.10.0, the new resources
vcd_rde_interface_behavior
andvcd_rde_type_behavior
allowed to define Behaviors for RDE Interfaces and RDE Types respectively.The Behaviors could be defined with the generic map
execution
argument, but the problem is that Terraform only supports simple maps of string->string, where one could be able to define executions of more complex structures, like a WebHook type does:Solution
Add a new attribute
execution_json
which is a plain string that represents a JSON. Bothexecution
andexecution_json
will live together, the first one being now just syntactic sugar for the latter.The challenge here is that the WebHook behavior type uses a special
_secure_
and_internal_
prefixes for fields that are write-only. So once created, they're never recovered from VCD. This causes dirty plans all the time, where the Provider asks for updates all the time. To avoid that, a new DiffSuppressFunc has been implemented:hasBehaviorExecutionChanged
, which ignores secure fields if the attributealways_update_secure_execution_properties
is disabled.Tests
☑️ Acceptance tests
☑️ Binary tests
☑️ Upgrade tests