Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulumi refresh does not detect changes when letter casing differs #5019

Closed
cermakp opened this issue Sep 20, 2024 · 0 comments
Closed

Pulumi refresh does not detect changes when letter casing differs #5019

cermakp opened this issue Sep 20, 2024 · 0 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@cermakp
Copy link

cermakp commented Sep 20, 2024

Describe the bug

When there is a difference in letter casing, the pulumi refresh command does not detect it. Example:

  • There is a Log Analytics workspace in Azure with the name "lawTestService"
  • The stack contains the same resource but with a different workspace name casing, like:
    "workspaceName": "lawtestservice"

If you run pulumi preview on the stack, no changes are detected.

Expected behavior
The pulumi preview command should detect changes in letter casing and synchronize the stack with the resource in Azure. As a result, the workspace name should be "lawTestService" in the stack.

@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 20, 2024
@cermakp cermakp closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant