Skip to content
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

Relax enum restrictions on Storage bypass parameter #4328

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

matthchr
Copy link
Member

@matthchr matthchr commented Oct 8, 2024

Fixes #4247.

Storage supports passing multiple values to the Bypass parameter separated by a comma, but that's not how Swagger enums work so the fact they've specified this field as an enum is technically incorrect. We just treat it as a string to allow the user to pass multiple values

If applicable:

  • this PR contains documentation
  • this PR contains tests
  • this PR contains YAML Samples

Fixes Azure#4247.

Storage supports passing multiple values to the Bypass parameter
separated by a comma, but that's not how Swagger enums work so the fact
they've specified this field as an enum is technically incorrect. We
just treat it as a string to allow the user to pass multiple values
@matthchr
Copy link
Member Author

matthchr commented Oct 9, 2024

/ok-to-test sha=2d7061b

@matthchr matthchr added this pull request to the merge queue Oct 9, 2024
Merged via the queue into Azure:main with commit 67a21e7 Oct 9, 2024
7 checks passed
@matthchr matthchr deleted the feature/storage-bypass-enum-fix branch October 9, 2024 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
2 participants