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

Add the ability to support default aliases in the bridge #607

Open
rshade opened this issue Sep 15, 2022 · 1 comment
Open

Add the ability to support default aliases in the bridge #607

rshade opened this issue Sep 15, 2022 · 1 comment
Labels
kind/enhancement Improvements or new features

Comments

@rshade
Copy link

rshade commented Sep 15, 2022

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Like azure-native, we need aliases configured with the previous provider name(s). A resource of before:mod:resource moved to after:mod:resource would have the former type token as an alias, and the new after SDK would adopt the resources seamlessly.

Affected area/feature

@rshade rshade added needs-triage Needs attention from the triage team kind/enhancement Improvements or new features labels Sep 15, 2022
@stack72 stack72 removed the needs-triage Needs attention from the triage team label Sep 16, 2022
@t0yv0
Copy link
Member

t0yv0 commented Feb 14, 2023

Hi Richard I think there's some solid progress toward this in #784 , as it came up as an internal urgent need on the @pulumi/ecosystem team also. We'll work this out shortly with the final shape of the API and let you know.

@t0yv0 t0yv0 mentioned this issue Mar 13, 2023
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

3 participants