Hello, getting a strange issue that I have never seen before. I tried pulumi up'ing without having made any changes to my stack and got this error.

error: rpc error: code = Unknown desc = ["region"]: provider mismatch (kind:DELETE  inputDiff:true != kind:DELETE_REPLACE  inputDiff:true)

It seems to be from a provider resource that was automatically created by pulumi as delineated by the default naming. I am not sure how to go about fixing this as I do not manage this resource within my code and pulumi refresh does not do anything.

This message was deleted.

This message was deleted.

Hi everyone, I'm trying to upgrade EKS NodeGroup from AL2 to AL2023, based on documentation:

Update the node group in place. Pulumi does this by first creating the new replacement nodes and then shutting down the old ones which will move pods to the new nodes forcibly. This is the default behavior when node groups are updated.

It seems does not happen to me. The preview shows the strategy is

replace

instead of

update

-> entire nodeGroup will be deleted first, then creating new nodeGroup, instead of update node by node.

pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:stack::eks::pulumi:pulumi:Stack::stack]
    --aws:eks/nodeGroup:NodeGroup: (delete-replaced)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
    +-aws:eks/nodeGroup:NodeGroup: (replace)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"
    ++aws:eks/nodeGroup:NodeGroup: (create-replacement)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"

Am I missing something?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello! I have a nested Pulumi config and one of the key has colon in its name. I want to add secrets under that key, but as far as

--path

option has format

<namespace>:<name>

Pulumi whether doesn't allow to set it, if I specify whole path with namespace, or does it in a wrong way, if I omit the namespace. For example: - With explicitly specified namespace:

pulumi config set --secret --path 'namespace:sites["<https://example.com>"].password' password

leads to error:

error: invalid configuration key: could not parse namespace:sites["<https://example.com>"].password as a configuration key (configuration keys should be of the form `<namespace>:<name>`)

- When namespace is omitted

pulumi config set --secret --path 'sites["<https://example.com>"].password' password

, there's no error, but config contains:

config:
  sites["<https://example>:
    com"]:
      password:
        secure: <secret>

Is there any way to workaround that? Pulumi

v3.116.1

.

This message was deleted.