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
Fix id validation for custom service and SLO to match what's actually usable #8939
Fix id validation for custom service and SLO to match what's actually usable #8939
Conversation
Hello! I am a robot. It looks like you are a: Community Contributor @NickElliot, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
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.
LGTM! Thanks for the update.
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 3 files changed, 7 insertions(+), 2 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccDataprocClusterIamPolicy |
Rerun these tests in REPLAYING mode to catch issues
|
… usable (GoogleCloudPlatform#8939) * Fix slo_id pattern in google_monitoring_slo * Fix servie_id pattern in google_monitoring_custom_service
… usable (GoogleCloudPlatform#8939) * Fix slo_id pattern in google_monitoring_slo * Fix servie_id pattern in google_monitoring_custom_service
Fixes hashicorp/terraform-provider-google#15825
The validation for the following id fields were too strict, so they have been adjusted to match the actual formats. Please refer to the issue for specific examples.
service_id
ongoogle_monitoring_custom_service
slo_id
ongoogle_monitoring_slo
I checked this documentation. Types of breaking changes | Magic Modules
This change relaxes the validation to contain the current pattern, so I think this is not a breaking change.
Do I need to add tests for the validation defined in regex? If so, I'll add it.
It would be helpful if you could advise on existing test cases for such a change.
Release Note Template for Downstream PRs (will be copied)