-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
tests(deck): add deck integration tests #12980
Conversation
848a0ac
to
36d07e9
Compare
36d07e9
to
73e79bd
Compare
96c451f
to
24746fb
Compare
decK integration tests✅ passed successfully. |
9cddf0c
to
81fe3ce
Compare
re-drafting to explore the option of using a review (by the bot) instead of a comment, to make the failures more visible when they occur Edit: done |
81fe3ce
to
8705c79
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.
decK integration tests
43ece33
to
edd4ea5
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.
decK integration tests
d4f3389
to
c4d7cf0
Compare
These tests are meant to catch changes in Kong that result in incompatibilities with decK. The approach used here is to configure all the bundled plugins in Kong and a few other entities and confirm that deck dump + sync executes without errors. This new workflow "continues-on-error" instead of producing failures on CI: changes in gateway schemas might have to be merged despite making decK fail, the purpose of this is to notify about such incompatibilities. When those failures are detected, the workflow posts a review in the PR requesting changes and with a link to the failing run. The review is then dismissed if new changes are pushed to the PR that make the workflow pass.
c4d7cf0
to
f03c57a
Compare
Successfully created cherry-pick PR for |
Summary
These tests are meant to catch changes in Kong that result in incompatibilities with decK.
The approach used here is to configure all the bundled plugins in Kong and a few other entities and confirm that deck dump + sync executes without errors.
This new workflow "continues-on-error" instead of producing failures on CI: changes in gateway schemas might have to be merged despite making decK fail, the purpose of this is to notify about such incompatibilities. When those failures are detected, the workflow posts a review in the PR requesting changes, and a link to the failing run.
The review is then dismissed if new changes are pushed to the PR that make the workflow pass.<-- not anymore: branch protection rules prevent thisChecklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
KAG-4236