AWS OIDC: List Deployed Database Services proto #49325
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcoandredinis
added
no-changelog
marcoandredinis
force-pushed
the
marco/awsoidc-listdatabaseservices
branch
from
6dc7b65 to
d5e82f0
Compare
atburke
approved these changes
Nov 22, 2024
marcoandredinis
force-pushed
the
marco/awsoidc-listdatabaseservices
branch
from
d5e82f0 to
c20b1dd
Compare
|
@zmb3 Can you please take a look when you get a chance? |
marcoandredinis
force-pushed
the
marco/awsoidc-listdatabaseservices
branch
from
c20b1dd to
7db738c
Compare
zmb3
approved these changes
Nov 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Teleport can deploy DatabaseServices automatically into the user's AWS account, using Amazon ECS. This happens during the Enroll New Resource / RDS flows. However, after the deployment, the user is left without any information about the deployed services. This PR adds a new gRPC service that exposes that information. Next PRs, will add implementation of that service and expose it in an HTTP endpoint.
marcoandredinis
force-pushed
the
marco/awsoidc-listdatabaseservices
branch
from
7db738c to
4e7bb9c
Compare
|
@marcoandredinis See the table below for backport results.
|
marcoandredinis
added a commit
that referenced
this pull request
Nov 28, 2024
Teleport can deploy DatabaseServices automatically into the user's AWS account, using Amazon ECS. This happens during the Enroll New Resource / RDS flows. However, after the deployment, the user is left without any information about the deployed services. This PR adds a new gRPC service that exposes that information. Next PRs, will add implementation of that service and expose it in an HTTP endpoint.
marcoandredinis
added a commit
that referenced
this pull request
Dec 2, 2024
Teleport can deploy DatabaseServices automatically into the user's AWS account, using Amazon ECS. This happens during the Enroll New Resource / RDS flows. However, after the deployment, the user is left without any information about the deployed services. This PR adds a new gRPC service that exposes that information. Next PRs, will add implementation of that service and expose it in an HTTP endpoint.
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 2, 2024
Teleport can deploy DatabaseServices automatically into the user's AWS account, using Amazon ECS. This happens during the Enroll New Resource / RDS flows. However, after the deployment, the user is left without any information about the deployed services. This PR adds a new gRPC service that exposes that information. Next PRs, will add implementation of that service and expose it in an HTTP endpoint.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Teleport can deploy DatabaseServices automatically into the user's AWS account, using Amazon ECS.
This happens during the Enroll New Resource / RDS flows.
However, after the deployment, the user is left without any information about the deployed services.
This PR adds a new gRPC service that exposes that information.
Next PRs, will add implementation of that service and expose it in an HTTP endpoint.