Skip to content

[BUG]: Microsoft.DocumentDB/mongoClusters/firewallRules - Name parameter regex pattern incorrect #34367

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

Open
AlexanderSehr opened this issue Apr 30, 2025 · 0 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.

Comments

@AlexanderSehr
Copy link

API Spec link

API Spec version

2024-02-15-preview

Describe the bug

There is a regex specified for the 'firewallRule' name parameter, that is ^[a-zA-Z0-9][-_.a-zA-Z0-9]* (ref), which is great, as it is pulled from here and published in all kinds of documentation.

There is one catch though, and that is that it 'seems' the regex is not 100% correct, and the character . is actually not allowed in the name.

Note: Using . was still working some 4-5 months ago for the given API version. Only afterwards it started to produce issues and it took us quite a while to figure out why (as there is no error and the deployment just times out)

Expected behavior

Either . should be removed from the validation pattern - or - if it should actually be alowed by the service.

Actual behavior

Trying to deploy a firewall-rule with a . in its name leads to an internal server error and a non-terminating deployment (i.e., it run's forever until it eventually times out).

Reproduction Steps

Try to deploy a firewall rule with . in its name. E.g. allow-1.2.3.4-to-5.6.7.8

Environment

No response

@AlexanderSehr AlexanderSehr added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 30, 2025
@olivertowers olivertowers self-assigned this Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.
Projects
None yet
Development

No branches or pull requests

2 participants