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

Unable to migrate resource between versions #2397

Closed
iwahbe opened this issue Apr 21, 2023 · 2 comments
Closed

Unable to migrate resource between versions #2397

iwahbe opened this issue Apr 21, 2023 · 2 comments
Labels
impact/usability Something that impacts users' ability to use the product easily and intuitively kind/bug Some behavior is incorrect or out of spec resolution/duplicate This issue is a duplicate of another issue

Comments

@iwahbe
Copy link
Member

iwahbe commented Apr 21, 2023

What happened?

A user attempted to switch from Pulumi.AzureNative.Databricks to Pulumi.AzureNative.Databricks.V20230201. This resulted in a replace being generated, instead of the expected no-op.

Expected Behavior

We expect this resource to be aliased as described in https://www.pulumi.com/registry/packages/azure-native/version-guide/.

Steps to reproduce

See https://pulumi-community.slack.com/archives/CRVK66N5U/p1682027492647039 for details.

Output of pulumi about

Pulumi 3.54.1
Pulumi.AzureNative 1.100.0
Pulumi CLI: 3.63.0

Additional context

Issue arose from Community Slack.

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).

@iwahbe iwahbe added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Apr 21, 2023
@rquitales rquitales added impact/usability Something that impacts users' ability to use the product easily and intuitively and removed needs-triage Needs attention from the triage team labels Apr 24, 2023
@mikhailshilkov
Copy link
Member

Context from Slack:

Pulumi Azure Native Databricks resource is defined inside my component resource. The databricks resource does have the parent property set to my component resource as well.

@mikhailshilkov mikhailshilkov added the resolution/duplicate This issue is a duplicate of another issue label Jul 13, 2023
@mikhailshilkov
Copy link
Member

It looks to be a duplicate of #2505 - I'll close in favour of the other issue that has more details

@mikhailshilkov mikhailshilkov closed this as not planned Won't fix, can't repro, duplicate, stale Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/usability Something that impacts users' ability to use the product easily and intuitively kind/bug Some behavior is incorrect or out of spec resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants