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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert Go Azure examples to fnOutput form #1115

Closed
t0yv0 opened this issue Nov 8, 2021 · 4 comments
Closed

Convert Go Azure examples to fnOutput form #1115

t0yv0 opened this issue Nov 8, 2021 · 4 comments
Assignees
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@t0yv0
Copy link
Member

t0yv0 commented Nov 8, 2021

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

pulumi/pulumi#5758 permits more elegant composition of datasources and resources, however there are no examples. IN #1094 we swept through existing examples but the only ones that were found in Go that would benefit from the new feature utilize pulumi-azure-native. Unfortunately, the feature is not rolled out to the Go build of pulumi-azure-native yet to minimize generated code size and avoid hitting some limits. Therefore the examples update is blocked.

Affected area/feature

@mikhailshilkov
Copy link
Member

@t0yv0 This should be unblocked now with azure-native v1.53.0.

@dixler
Copy link
Contributor

dixler commented Jan 21, 2022

@mikhailshilkov

merged #1154

in examples/azure-go-containerapps, I attempted bumping azure-native to 1.53.0, but ran into an issue with pulumi/pulumi-azure-native's spec being ahead of the deployed changes according to this issue.

@t0yv0
Copy link
Member Author

t0yv0 commented Jan 21, 2022

Let's close this one is done.

@t0yv0 t0yv0 closed this as completed Jan 21, 2022
@pulumi-bot
Copy link

Cannot close issue without required labels: resolution/

@pulumi-bot pulumi-bot reopened this Jan 21, 2022
@t0yv0 t0yv0 added the resolution/fixed This issue was fixed label Jan 21, 2022
@t0yv0 t0yv0 closed this as completed Jan 21, 2022
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 resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

4 participants