Anton Tayanovskyy

Thanks for your interest @alayshia ! Resource support in this Provider tracks the upstream TF provider which has a request for Managed Blockchain in https://github.com/hashicorp/terraform-provider-aws/issues/15424 Unfortunately looks like the upstream...

@pierskarsenbarg we have a fix coming shortly that will actually re-create the resources in the provider. Would that work? We're actually intending to deploy https://github.com/pulumi/pulumi-aws/pull/3497 but I'd love to hear...

Thanks for reporting this @armaneous , I'm sorry this does not work as expected. Our team will be taking a look subject to time availability.

CC @mjeffryes I'm not sure which epic - I've been labelling these as bug/diff for the moment. On the surface it looks very much like one of those issues. @armaneous...

Thanks for the feature request @stooj ! At a glance it appears that https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/appsync_graphql_api could have supported environment variables, in which case this Pulumi projected provider would land the functionality...

Looks like the regression test is catching an actual problem. We introduced custom retry for KMS condition on lambda invocation and it has regressed because upstream is moving from Go...

Fixed the patch to use AWS SDKv2 and trying this again.

aws_bedrockagent_agent_knowledge_base_association mapping to bedrock/agentAgentKnowledgeBaseAssociation.AgentAgentKnowledgeBaseAssociation is unfortunate, perhaps can do better here.

TestAccWebserverComp flake.

I can trigger this panic on the following program. Do `pulumi up` twice, second `pulumi up` panics: ```python import pulumi import json import pulumi_aws as aws test = aws.batch.JobDefinition("test", name="my_test_batch_job_definition",...