chore: dynatrace_platform_slo remove character length checks#991
Merged
chore: dynatrace_platform_slo remove character length checks#991
dynatrace_platform_slo remove character length checks#991Conversation
Each change on the API side would mean that we have to update and release the provider to match the character length. As this is not feasible, we decide to not do any character length validation
Kirdock
force-pushed
the
chore/update-platform-slo-validation
branch
from
7023663 to
d19a7d8
Compare
arthurpitman
approved these changes
Feb 23, 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?
The API for platform SLOs now sets a higher character limit for certain fields. Therefore, we need to update our validation.
What has changed?
Character length validation is no longer performed locally.
How does it do it?
By removing all character length checks.
Each change on the API side would mean that we have to update and release the provider to match the character length. As this is not feasible, we decide not to do any character length validation
How is it tested?
Manual tests (removed limitation)
How does it affect users?
The character length validation now solely depends on the API.
Issue: CA-18236