Peter Woodworth

Thanks for the request @der-eismann, We'll start thinking about our next major version release so that we can support this 🙂

Thanks everyone for letting us know about the need to upgrade the Node runtime for this action. We cannot merge these PRs as they are unfortunately, because to make this...

v2 will run at least Node 16 😃

It's already here @leonk-sportsbet! But we have that on a separate branch `v1-node16`, so you will want to configure your action to use `aws-actions/configure-aws-credentials@v1-node16`. See [this comment](https://github.com/aws-actions/configure-aws-credentials/issues/489#issuecomment-1278145876) for more information...

Sorry to hear you're running into this issue @Office-Manager, I'm not able to reproduce this, here's my trust policy: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": {...

Another thing I can think of that might apply here is that if you are using an [environment](https://docs.github.com/en/actions/using-jobs/using-environments-for-jobs) or the job is triggered by a PR, then GitHub will not...

@seebees I'm not finding much information on `ACTIONS_ID_TOKEN_REQUEST_TOKEN` environment variable. Can you explain and share documentation around what exactly this variable is for?

I'm confused in how you're arriving to the conclusion that the lack of existence of this variable means that permissions have not been set. I came across this documentation before...

I'm not finding that any of the children of Vpc which are considered taggable are lacking the tag attached through the aspect. > namely: DHCPOptions, NetworkAcl, RouteTable and SecurityGroup None...

Yeah none of these resources you've mentioned are actually appearing in the CloudFormation template, meaning that CDK has no control over those resources. They are likely getting created automatically by...