Vivek Lakshmanan

Thanks for opening the issue @caboog. I have added this to our backlog and the team will look to prioritize it.

@danielrbradley this looks like a bug in CloudControl - we would expect the get to CloudControl to return the tags as well if the outputs don't contain the tags. @henriiik...

Apologies. IgnoreChanges is not the right suggestion. As demonstrated by @henriiik in https://github.com/pulumi/pulumi-aws-native/issues/415#issuecomment-1091063070 setting the description and some tag value at creation time avoids the overeager validation. FWIW this is...

FWIW json schemas are often pretty scant on the descriptions so at the moment, our api docs are pretty anemic when it comes to property descriptions. See https://github.com/pulumi/pulumi-aws/issues/2436 for instance.

FYI @danielrbradley

On a related note, I am also curious what our semantics on "unsetting" or overriding the replacement logic specified in the schema for a resource should be. i.e. in https://github.com/pulumi/pulumi/pull/7226...

Have you considered nodegroupv2? Its just recently added and it has a few bugs we are tracking but that might give you the control you want. ManagedNodeGroup is more opinionated.

As mentioned in #1504, this may also help in case of network issues.

I am fairly certain this is because of a validation failure in the CFN provisioner used by cloudcontrol API. Would you be able to provide a minimal repro (apologies I...

I believe this is an instance where CloudControl is returning the wrong identifier back? Trying this out and capturing the payload for the requests should help.