From d48810860805af4917eaf10f2b43591a23d9447b Mon Sep 17 00:00:00 2001 From: Torian Crane Date: Fri, 17 Nov 2023 11:48:38 +0000 Subject: [PATCH] added sub ID bug note --- aws-py-oidc-provider-pulumi-cloud/README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/aws-py-oidc-provider-pulumi-cloud/README.md b/aws-py-oidc-provider-pulumi-cloud/README.md index f142d0d1a..980b0cf74 100644 --- a/aws-py-oidc-provider-pulumi-cloud/README.md +++ b/aws-py-oidc-provider-pulumi-cloud/README.md @@ -93,6 +93,19 @@ You can configure more granular access control by adding the `sub` claim to the ] } ``` + +{{< notes type="warning" >}} + +If you are integrating Pulumi ESC with Pulumi IaC, using the specific name of the ESC environment in the subject identifier will not work at this time. There is a [known issue](https://github.com/pulumi/pulumi/issues/14509) with the value of the subject identifier that is sent to the provider from Pulumi. + +The steps in this guide will work for Pulumi ESC if you use the following syntax instead: + +`pulumi:environments:org::env:` + +Make sure to replace `` with the name of your Pulumi organization and use the literal value of `` as shown above. + +{{< /notes >}} + Once you are done, you can destroy all of the resources as well as the stack: ```bash