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

[v16] make configure awsoidc-idp transparent #47178

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

GavinFrazar
Copy link
Contributor

Backport #46747 to branch/v16

Applies to the integration command that the web UI discover flows tell
users to run in AWS CloudShell to setup the AWS OIDC identity provider:
    teleport integration configure awsoidc-idp

The command describes itself, its actions, and the desired state after
it runs. It then prompts the user (by default) to confirm the action
plan before proceeding.
The confirmation prompt can be overridden with cli flag --confirm
if desired.

The IAM role it configures is no longer required to have the "ownership"
tags that teleport applies if it's created by teleport, since the user is
now prompted for confirmation before making changes.
This allows a user to configure an existing IAM role without tagging the
role for configuration by teleport.
The command will still attempt to ensure the IAM role it configures has
teleport tags, but failing to do so is only a warning.
@GavinFrazar GavinFrazar added the no-changelog Indicates that a PR does not require a changelog entry label Oct 3, 2024
@github-actions github-actions bot added backport database-access Database access related issues and PRs size/lg labels Oct 3, 2024
@GavinFrazar GavinFrazar added this pull request to the merge queue Oct 7, 2024
Merged via the queue into branch/v16 with commit 4742a88 Oct 7, 2024
43 of 44 checks passed
@GavinFrazar GavinFrazar deleted the bot/backport-46747-branch/v16 branch October 7, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport database-access Database access related issues and PRs no-changelog Indicates that a PR does not require a changelog entry size/lg
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants