-
Notifications
You must be signed in to change notification settings - Fork 98
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
Functional tests for UpstreamSettings Policy #2869
Functional tests for UpstreamSettings Policy #2869
Conversation
@salonichf5 looks like you need to rebase on main |
b4c4663
to
a2d98fc
Compare
a2d98fc
to
829fbd4
Compare
I rebased it from the feature branch for UpstreamSettings Policy to leverage the CRD for the functional tests and the base branch is the same as well |
@salonichf5 We want to target the upstream settings policy branch for this PR, not main. Sorry for the confusion. |
829fbd4
to
1b13c21
Compare
tests/suite/manifests/upstream-settings-policy/invalid-usps.yaml
Outdated
Show resolved
Hide resolved
tests/suite/manifests/upstream-settings-policy/invalid-usps.yaml
Outdated
Show resolved
Hide resolved
b69c193
to
37d91e4
Compare
723d1c6
to
ca42375
Compare
05cb89f
to
17f5a7c
Compare
054e73c
to
bb30486
Compare
bb30486
to
6e267ea
Compare
722bf2a
to
d33da67
Compare
d33da67
to
3d09142
Compare
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.
🚀
48ecf2e
into
nginxinc:feature/upstream-settings-policy
Functional Tests for UpstreamSettings Policy.
Functional Tests for UpstreamSettings Policy.
Functional Tests for UpstreamSettings Policy.
Closes #2736
Checklist
Before creating a PR, run through this checklist and mark each as complete.
Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.