-
Notifications
You must be signed in to change notification settings - Fork 41
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
ManagedEnvironment - Name -> EnvironmentName causing a replace #2305
Comments
Hi @michaelmcneilnet sorry the upgrade is not as smooth as it should be. Unfortunately this was quite a breaking changed introduced upstream by Azure/azure-rest-api-specs#19005 This general problem is being tracked in pulumi/pulumi#9115. The workaround right now is to either:
|
Hi @danielrbradley thank you for the prompt response. I went with the manual editing of the stack json,
but am still facing a replace, with the following output in preview
The only change I made in the json was to replace This is the section of json I changed, is that correct? (second last line) "urn": "urn:pulumi:prod::xxx::azure-native:app:ManagedEnvironment::ManagedEnvironment",
"custom": true,
"id": "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.App/managedenvironments/xxx",
"type": "azure-native:app:ManagedEnvironment",
"inputs": {
"appLogsConfiguration": {
"destination": "log-analytics",
"logAnalyticsConfiguration": {
"customerId": "xxx",
"sharedKey": "xxx"
}
},
"location": "northeurope",
"environmentName": "xxx",
"resourceGroupName": "xxx"
} |
Looks like it was the |
What happened?
On Upgrading from Pulumi.AzureNative 1.64.1 -> 1.97.0 we see that
ManagedEnvironmentArgs.Name
has been replaced withManagedEnvironmentArgs.EnvironmentName
. When we change to useEnvironmentName
, onpulumi up
, we see it wants to replace the ManagedEnvironment.How can we avoid a replacement?
Expected Behavior
Not to replace the environment.
Steps to reproduce
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: