You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
➜ typescript git:(main) ✗ pulumi about
CLI
Version 3.116.1
Go Version go1.22.2
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.33.1
resource kafka 3.7.1
resource kubernetes 4.11.0
language nodejs unknown
resource postgresql 3.11.0
Host
OS darwin
Version 14.4.1
Arch arm64
This project is written in nodejs: executable='***' version='v20.11.1'
Backend
Name ***
URL file://~
User ***
Organizations
Token type personal
Dependencies:
NAME VERSION
@pulumi/kafka 3.7.1
@pulumi/kubernetes 4.11.0
@pulumi/pulumi 3.115.1
ts-pattern 5.0.6
yaml 2.4.2
typescript 5.4.5
@pulumi/aws 6.33.1
@pulumi/postgresql 3.11.0
@types/node 20.10.5
Pulumi locates its logs in /var/folders/s_/rr4bg4qx7hv__l9g4fqw987w0000gq/T/ by default
warning: Failed to get information about the current stack: No current stack
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue @soujiro32167. I am able to reproduce this. Note that the same issue also exists for ConfigMaps if we set CMs to be mutable within our k8s provider setup. The issue doesn't exist for CMs in the repro, since our provider is doing a replacement, which goes through a different flow for saving state compared to an update flow.
### Proposed changes
Always store `newInputs` to avoid spurious diffs in renderYaml updates.
Storing `oldLive` in state will result in the Pulumi state never
updating after the initial create.
Testing: added a new step within the `TestRenderYAML` that exercises the
update flow. This test fails without the changes in this PR.
### Related issues (optional)
Fixes: #3026
What happened?
Using a kubernetes provider with
renderYamlToDirectory
, I want to create a deployment and configmap.The resources get created successfully. After a second
pulumi up
, no changes are observed.However, after updating the deployment, the pulumi state will not update. Updating the configmap works fine
To reproduce:
pulumi up -s repro
containerPort: 9090
pulumi up -s repro --diff
shows the diff correctlyyes
to apply the changespulumi up -s repro --diff
shows the same diff, even though the change was already appliedNote: the yaml
yamls/apps_v1-deployment-myns-my-deployment.yaml
gets updated correctlyExample
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: