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

Don't use *schema.Package in nodejs codegen #11589

Merged
merged 1 commit into from Dec 8, 2022
Merged

Conversation

iwahbe
Copy link
Member

@iwahbe iwahbe commented Dec 8, 2022

Part of #9932
Builds on #11578

tldr: Package is not reliable when its used for an external package. We are transferring over to PackageReference, and will remove the Package field once all references to it have been removed.

@iwahbe iwahbe self-assigned this Dec 8, 2022
@iwahbe iwahbe added language/javascript impact/no-changelog-required This issue doesn't require a CHANGELOG update labels Dec 8, 2022
@pulumi-bot
Copy link
Contributor

Changelog

[uncommitted] (2022-12-08)

@iwahbe iwahbe added the area/codegen SDK-gen, program-gen, convert label Dec 8, 2022
@iwahbe
Copy link
Member Author

iwahbe commented Dec 8, 2022

bors r+

@bors
Copy link
Contributor

bors bot commented Dec 8, 2022

🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set.

bors bot added a commit that referenced this pull request Dec 8, 2022
11589: Don't use `*schema.Package` in nodejs codegen r=iwahbe a=iwahbe

Part of #9932
Builds on #11578

tldr: Package is not reliable when its used for an external package. We are transferring over to PackageReference, and will remove the Package field once all references to it have been removed.

11592: Don't use `*schema.Package` in .NET codegen r=iwahbe a=iwahbe

Part of #9932
Builds on #11578

tldr: Package is not reliable when its used for an external package. We are transferring over to PackageReference, and will remove the Package field once all references to it have been removed.

11593: Interpret schema.Asset as pcl.AssetOrArchive r=iwahbe a=iwahbe

Fixes #11572

Co-authored-by: Ian Wahbe <ian@wahbe.com>
@bors
Copy link
Contributor

bors bot commented Dec 8, 2022

Build failed (retrying...):

bors bot added a commit that referenced this pull request Dec 8, 2022
11559: fix(sdk/python): Allow for duplicate output values in python programs r=kpitzen a=kpitzen

I used the node SDK as inspiration for this change - there were a few things we were doing differently in python (specifically handling all cases in the outer layer of `massage` rather than allowing for more fine-grained control in a `massage_complex` function like in node.  We also take the stack concept from the node SDK to resolve the immediate issue of duplicate outputs.

<!--- 
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

Fixes #11133 

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [x] I have added tests that prove my fix is effective or that my feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->


11588: Don't use *schema.Package in go codegen r=iwahbe a=iwahbe

Part of #9932
Builds on #11578

tldr: Package is not reliable when its used for an external package. We are transferring over to PackageReference, and will remove the Package field once all references to it have been removed.

11589: Don't use `*schema.Package` in nodejs codegen r=iwahbe a=iwahbe

Part of #9932
Builds on #11578

tldr: Package is not reliable when its used for an external package. We are transferring over to PackageReference, and will remove the Package field once all references to it have been removed.

Co-authored-by: Kyle Pitzen <kylepitzen@Kyles-MBP.fios-router.home>
Co-authored-by: Ian Wahbe <ian@wahbe.com>
@bors
Copy link
Contributor

bors bot commented Dec 8, 2022

Build failed (retrying...):

@bors
Copy link
Contributor

bors bot commented Dec 8, 2022

Build succeeded:

@bors bors bot merged commit 6f68060 into master Dec 8, 2022
@bors bors bot deleted the iwahbe/nodejs-ref-only branch December 8, 2022 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/codegen SDK-gen, program-gen, convert impact/no-changelog-required This issue doesn't require a CHANGELOG update language/javascript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants