tool · inferred from evidence
pulumi preview
A Pulumi command mentioned as hanging in GitHub Actions.
- Error: pulumi:providers:aws resource 'default' has a problem: Invalid credentials configured
Fixes the Pulumi AWS provider rejecting the configured credentials. For engineers whose keys or session are present but invalid, covering rotation, typos, and revoked keys.
- Error: passphrase must be the same as the last time the stack was updated
Fixes Pulumi rejecting a changed secrets passphrase on an existing stack. For engineers who rotated PULUMI_CONFIG_PASSPHRASE and now cannot update, the passphrase is baked into state encryption and cannot be changed in place.
- Error: Server-Side Apply field conflict detected on Pulumi Kubernetes resource
Fixes Pulumi Kubernetes failing to adopt resources after switching to an explicit provider. For engineers who added an explicit provider and now hit server-side apply conflicts, with the delete-and-recreate vs import choice.
- Error: could not load provider for resource: could not find provider
Fixes Pulumi destroy or update failing because state references a provider version that is no longer installed. For engineers who upgraded the CLI or provider and now cannot even destroy, with the stack-export surgery fix.
- Error: malformed RPC secret value missing value for "connection"
Fixes Pulumi destroy failing after a state export taken with the wrong passphrase silently nulled every secret. For engineers whose stack export/import pipeline corrupted secrets, explaining the malformed RPC secret error and how to avoid i
- Error: passphrase must be set with PULUMI_CONFIG_PASSPHRASE (on a KMS-encrypted stack)
Fixes Pulumi demanding a passphrase on a stack that uses AWS KMS for secrets. For teams on S3 backends whose CI suddenly asks for PULUMI_CONFIG_PASSPHRASE, the cause is the local stack YAML losing its KMS metadata.
- Error: pulumi:providers:aws resource 'default' has a problem: No valid credential sources found
Fixes the Pulumi AWS provider failing at preview with no valid credential sources. For engineers running Pulumi against AWS who see the provider registration fail and need to get credentials into the chain, via environment, shared config, S