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

Backport of [API Gateway] Validate listener name is not empty into release/1.15.x #16341

Conversation

hc-github-team-consul-core
Copy link
Contributor

Backport

This PR is auto-generated from #16340 to be assessed for backporting due to the inclusion of the label backport/1.15.

The below text is copied from the body of the original PR.


Description

This adds the same validation rules that the API Gateway spec has for listener names. Previously we were allowing for an empty listener name which made it impossible to distinguish between wanting to bind to all listeners on a gateway or just the listener without a name.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/api-gateway-listener-name-validation/instantly-smooth-loon branch 2 times, most recently from d8262fd to 7b7078f Compare February 21, 2023 19:12
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@github-actions github-actions bot added the theme/api Relating to the HTTP API interface label Feb 21, 2023
@hc-github-team-consul-core hc-github-team-consul-core merged commit 1241135 into release/1.15.x Feb 21, 2023
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/api-gateway-listener-name-validation/instantly-smooth-loon branch February 21, 2023 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/api Relating to the HTTP API interface
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants