From cd7547c84ab2355d64dcd4213ee9de43629a2608 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Germ=C3=A1n=20Lena?= Date: Thu, 16 May 2024 10:09:36 -0700 Subject: [PATCH] Update themes/default/content/docs/pulumi-cloud/deployments/customer-managed-agents.md Co-authored-by: Eric Rudder --- .../docs/pulumi-cloud/deployments/customer-managed-agents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/themes/default/content/docs/pulumi-cloud/deployments/customer-managed-agents.md b/themes/default/content/docs/pulumi-cloud/deployments/customer-managed-agents.md index 0e3dae0b85..f93665d477 100644 --- a/themes/default/content/docs/pulumi-cloud/deployments/customer-managed-agents.md +++ b/themes/default/content/docs/pulumi-cloud/deployments/customer-managed-agents.md @@ -48,7 +48,7 @@ If you are running the agent inside a firewall ensure to allow outbound requests It is possible to use OpenID authentication to fetch Pulumi Pool tokens dynamically instead ofconfiguring a static token for the agents. You must first register the OpenID provider as a trusted OIDC issuer in your Pulumi account, as documented at [OIDC documentation](/docs/pulumi-cloud/oidc/client). -After that, there are a few configurations required by the agent: +After registering the provider, this other information is required by the agent: - `organization_name`: your Pulumi organization name - `runner_pool_id`: the pool id the instance will connect to