-
Notifications
You must be signed in to change notification settings - Fork 485
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
feat(security): Implement consul token header in API Gateway #3391
feat(security): Implement consul token header in API Gateway #3391
Conversation
26176fb
to
3daad41
Compare
cmd/security-bootstrapper/entrypoint-scripts/kong_wait_install.sh
Outdated
Show resolved
Hide resolved
3daad41
to
435fc41
Compare
435fc41
to
88d5918
Compare
rebased against master and removed the previous beaus' commit; now it only contains the stuff for adding consul route and header into Kong. |
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.
LGTM
- Add implementation for enabling request transformer plugin on consul service for Kong's route through proxy-setup - Fix unit test issues - Add necessary starting sequence and env. for proxy-setup in snap packaging Closes: edgexfoundry#3368 Signed-off-by: Jim Wang <[email protected]>
Signed-off-by: Jim Wang <[email protected]>
88d5918
to
534e16a
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
no consul service available in Kong
Issue Number: #3368
What is the new behavior?
add consul service/route to Kong and enable consul header through kong's request transform plugins on the added consul service.
Does this PR introduce a breaking change?
New Imports
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Note: This has been
re-based
on top of @beaufrusetta's branch from his PR #3328Would need some merging coordination with his PR: until then, made this PR as draft.
Beau's PR has already merged, updated to fit only commits I've now.
Other information