feat: update dynatrace_openpipeline_v2_* resources to 1.51#982
Merged
feat: update dynatrace_openpipeline_v2_* resources to 1.51#982
Conversation
Also slightly changed/updates the existing empty-set workaround to be more future proof. Adds new properties and preconditions
Also slightly changed/updates the existing empty-set workaround to be more future proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
Also slightly changed/updated the existing empty-set workaround to be more future-proof. Adds new properties and preconditions
dynatrace/api/builtin/openpipeline/bizevents/ingestsources/settings/field_extraction_entry.go
Show resolved
Hide resolved
dynatrace/api/builtin/openpipeline/bizevents/ingestsources/settings/field_extraction_entry.go
Show resolved
Hide resolved
dynatrace/api/builtin/openpipeline/bizevents/ingestsources/settings/field_extraction_entry.go
Show resolved
Hide resolved
dynatrace/api/builtin/openpipeline/bizevents/pipelines/settings/field_extraction_entry.go
Show resolved
Hide resolved
dynatrace/api/builtin/openpipeline/bizevents/pipelines/settings/settings.go
Show resolved
Hide resolved
dynatrace/api/builtin/openpipeline/davis/events/ingestsources/settings/bizevent_attributes.go
Show resolved
Hide resolved
d0weinberger
approved these changes
Feb 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why this PR?
Some resources need to be updated.
Some were still on
1.34.1, where they aren't compatible with pipeline groupsWhat has changed?
Resources are updated to match the current payload.
How does it do it?
field_extraction_entryaddedextraction_type. Fallback to the set default value added.field_extraction_entry(due to the extraction_type and related conditional properties)Possible Values:...=>Possible values:...)For the older resources that were still on
1.34.1event_typefield to be setHow is it tested?
Existing tests for the empty-set-bug updated
How does it affect users?
They can now configure the resource to work with pipeline groups
Issue: CA-18100