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

Dotnet version, and official support? #17

Open
ffMathy opened this issue May 11, 2023 · 5 comments
Open

Dotnet version, and official support? #17

ffMathy opened this issue May 11, 2023 · 5 comments

Comments

@ffMathy
Copy link

ffMathy commented May 11, 2023

This is awesome.

We could technically offer this for Pulumi for dotnet as well, I think.

@xShteff
Copy link
Member

xShteff commented May 11, 2023

We could technically offer this for Pulumi for dotnet as well, I think.

Oh interesting. I actually never really tried Pulumi with .NET but perhaps we could join forces into creating this as a monorepo :).

We might be able to keep the semantic-release setup to publish the NuGet package, I see they have an extension for it! https://www.npmjs.com/package/semantic-release-nuget

@mbogh
Copy link
Collaborator

mbogh commented May 11, 2023

Let's go, the .NET implementation would most likely give a nicer call site.

Also would make sense to restructure the project to follow what Pulumi does with their packages https://github.com/pulumi/pulumi-random

@ffMathy
Copy link
Author

ffMathy commented Jul 24, 2023

Perhaps we can even "persuade" Pulumi to offer this out of the box? Has anyone tried this before?

@ffMathy ffMathy changed the title Thanks for this! Dotnet version, and official support? Jul 24, 2023
@ffMathy
Copy link
Author

ffMathy commented Jul 24, 2023

Filed an issue here. Fingers crossed!

pulumi/pulumi#13568

@xShteff
Copy link
Member

xShteff commented Jul 24, 2023

Perhaps we can even "persuade" Pulumi to offer this out of the box? Has anyone tried this before?

Could be worth a shot, sure.

They do have a Output.get function that would theoretically get the value of the Output, but this is only callable post-deployment and will throw an error while deploying or previewing the stack:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants