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
Running the examples/eventhub program, the EventHubNamespace resource always produces a diff because of sku: "standard" - this is returned as sku: "Standard" from the cloud.
Most other resources have this property patched to be case insensitive - this resource probably needs that too.
pulumi about
CLI
Version 3.108.1
Go Version go1.22.0
Go Compiler gc
Plugins
NAME VERSION
azure 4.42.0
nodejs unknown
Host
OS darwin
Version 14.1.1
Arch arm64
This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v21.6.1'
Backend
Name pulumi.com
URL https://app.pulumi.com/venelin-pulumi-corp
User venelin-pulumi-corp
Organizations venelin-pulumi-corp, demo, pulumi
Token type personal
Pulumi locates its logs in /var/folders/82/nqnqw81s1h56l5nv940f9mq00000gn/T/ by default
warning: Failed to get information about the Pulumi program's dependencies: failed to run "/opt/homebrew/bin/npm ls --json --depth=0": exit status 1
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:
What happened?
Running the
examples/eventhub
program, theEventHubNamespace
resource always produces a diff because ofsku: "standard"
- this is returned assku: "Standard"
from the cloud.Most other resources have this property patched to be case insensitive - this resource probably needs that too.
Example
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: