-
Couldn't load subscription status.
- Fork 3
chore: fix regex validation to enforce exact match (public or private) #520
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
Conversation
|
/run pipeline |
1 similar comment
|
/run pipeline |
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.
There are a couple of other instances of the pattern being fixed.
Not 100% match, but the same logic applies to service_endpoints.
condition = can(regex("public|public-and-private|private", var.service_endpoints))
in 2 places.
|
/run pipeline |
1 similar comment
|
/run pipeline |
|
/run pipeline |
1 similar comment
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
🎉 This PR is included in version 2.3.16 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
https://github.ibm.com/GoldenEye/issues/issues/15651
Fix regex validation to enforce exact match (public or private)