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

Expose webhook, callback on different ingress #1527

Open
dawidmalina opened this issue Nov 11, 2024 · 2 comments
Open

Expose webhook, callback on different ingress #1527

dawidmalina opened this issue Nov 11, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@dawidmalina
Copy link
Contributor

Feature description 💡

No sure if this is currently possible from the code perspective but I would like to expose only part of the api related to VCS endpoints callback and webhook on dedicated public ingress, keeping remaining part purely internal.

If this is already available please help me with configuration.

Anything else?

No response

@dawidmalina dawidmalina added the enhancement New feature or request label Nov 11, 2024
@alfespa17
Copy link
Member

I guess you will have to create a second ingress configuration when you are deploying the app and allow the following endpoints:

  • /.well-known/jwks (for dynamic credentials if you are planning to use that)
  • /.well-known/openid-configuration (for dynamic credentials if you are planning to use that)
  • /callback/v1/**
  • /webhook/v1/**

I guess that should work for you

@dawidmalina
Copy link
Contributor Author

Thanks for the quick reply:) I will try to validate that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants