-
Notifications
You must be signed in to change notification settings - Fork 1.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
HTTP Endpoint to return Integration Summary (Dashboard) #48994
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
ea1dd29
to
05c6bc5
Compare
Should the URL be |
Changed to |
05c6bc5
to
e70652f
Compare
e70652f
to
647776e
Compare
This PR adds a new endpoint which returns the summary of an integration: - EC2, RDS and EKS found and enrolled resources It will be used to let the user know about what's the current state of the integration. PS: the number of deployed ECS agents is not yet filled, but will be as soon as the other PR lands.
647776e
to
1b0025e
Compare
@marcoandredinis See the table below for backport results.
|
* AWS OIDC Dashboard: Auto Discovery summary endpoint This PR adds a new endpoint which returns the summary of an integration: - EC2, RDS and EKS found and enrolled resources It will be used to let the user know about what's the current state of the integration. PS: the number of deployed ECS agents is not yet filled, but will be as soon as the other PR lands. * fix integration stats path * improve comment on rule counter * deduplicate code/
) * AWS OIDC Dashboard: Auto Discovery summary endpoint This PR adds a new endpoint which returns the summary of an integration: - EC2, RDS and EKS found and enrolled resources It will be used to let the user know about what's the current state of the integration. PS: the number of deployed ECS agents is not yet filled, but will be as soon as the other PR lands. * fix integration stats path * improve comment on rule counter * deduplicate code/
This PR adds a new endpoint which returns the summary of an integration:
It will be used to let the user know about what's the current state of
the integration.
PS: the number of deployed ECS agents is not yet filled, but will be as
soon as the other PR lands.
Demo:
curl 'https://proxy.example.com/v1/webapi/sites/proxy.example.com/integrations/teleportdev/stats' --silent ... | jq