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
pulumi convert
to Go generates incorrect code and go.mod
for component usage
#11427
Comments
I've transferred the issue from pulumi-yaml to pu/pu. The generated PCL looks correct, and other languages generate valid code. I think this is a problem with the go language generator. Generated PCL:
|
11431: Bumps grpcio to version 1.50 r=kpitzen a=kpitzen Currently, pinning to a version of grpcio <1.50 can cause build errors on newer versions of python+pip - the existing setup.py install method of building libararies is being deprecated and wheels are not being backported for older versions of grpcio. Since this change is a no-op as far as our python proto clients are concerned, it feels safe to bump to a version that will be supported going forward <!--- 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 #11276 Though this change doesn't result in guaranteed Python 3.11 support, it should allow users of Python 3.11 to at least install Pulumi successfully without Deprecation warnings etc. grpcio 1.4X does not ship 3.11-compatible wheels, so users are starting to see errors when installing Pulumi - bumping to this version also does not change our existing proto clients in Python, so feels like a relatively safe change. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] 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. --> 11437: Mark external modules as forign r=iwahbe a=iwahbe Fixes #8070 Progress on #11427 Co-authored-by: Kyle Pitzen <kyle.pitzen@gmail.com> Co-authored-by: Ian Wahbe <ian@wahbe.com>
11431: Bumps grpcio to version 1.50 r=kpitzen a=kpitzen Currently, pinning to a version of grpcio <1.50 can cause build errors on newer versions of python+pip - the existing setup.py install method of building libararies is being deprecated and wheels are not being backported for older versions of grpcio. Since this change is a no-op as far as our python proto clients are concerned, it feels safe to bump to a version that will be supported going forward <!--- 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 #11276 Though this change doesn't result in guaranteed Python 3.11 support, it should allow users of Python 3.11 to at least install Pulumi successfully without Deprecation warnings etc. grpcio 1.4X does not ship 3.11-compatible wheels, so users are starting to see errors when installing Pulumi - bumping to this version also does not change our existing proto clients in Python, so feels like a relatively safe change. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] 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. --> 11437: Mark external modules as forign r=iwahbe a=iwahbe Fixes #8070 Progress on #11427 Co-authored-by: Kyle Pitzen <kyle.pitzen@gmail.com> Co-authored-by: Ian Wahbe <ian@wahbe.com>
Progress so far:
|
11431: Bumps grpcio to version 1.50 r=kpitzen a=kpitzen Currently, pinning to a version of grpcio <1.50 can cause build errors on newer versions of python+pip - the existing setup.py install method of building libararies is being deprecated and wheels are not being backported for older versions of grpcio. Since this change is a no-op as far as our python proto clients are concerned, it feels safe to bump to a version that will be supported going forward <!--- 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 #11276 Though this change doesn't result in guaranteed Python 3.11 support, it should allow users of Python 3.11 to at least install Pulumi successfully without Deprecation warnings etc. grpcio 1.4X does not ship 3.11-compatible wheels, so users are starting to see errors when installing Pulumi - bumping to this version also does not change our existing proto clients in Python, so feels like a relatively safe change. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] 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. --> 11437: Mark external modules as forign r=justinvp a=iwahbe Fixes #8070 Progress on #11427 11440: Cleanup import generation r=iwahbe a=iwahbe Cleanup the `getPulumiImport` function. In doing so, remove an edge causing extraneous `/index` in #11427. For reviewers, looking at the diff for this PR is painful. It's much easier to review the old and new code separately. Part of #11427. 11441: Changelog and go.mod updates for v3.47.2 r=pulumi-bot a=pulumi-bot bors merge Co-authored-by: Kyle Pitzen <kyle.pitzen@gmail.com> Co-authored-by: Ian Wahbe <ian@wahbe.com> Co-authored-by: github-actions <github-actions@github.com>
Filed issue: pulumi/pulumi-aws-apigateway#64.
It sets the base path as We can see a correct example in the |
11440: Cleanup import generation r=iwahbe a=iwahbe Cleanup the `getPulumiImport` function. In doing so, remove an edge causing extraneous `/index` in #11427. For reviewers, looking at the diff for this PR is painful. It's much easier to review the old and new code separately. Part of #11427. 11441: Changelog and go.mod updates for v3.47.2 r=pulumi-bot a=pulumi-bot bors merge Co-authored-by: Ian Wahbe <ian@wahbe.com> Co-authored-by: github-actions <github-actions@github.com>
11431: Bumps grpcio to version 1.50 r=kpitzen a=kpitzen Currently, pinning to a version of grpcio <1.50 can cause build errors on newer versions of python+pip - the existing setup.py install method of building libararies is being deprecated and wheels are not being backported for older versions of grpcio. Since this change is a no-op as far as our python proto clients are concerned, it feels safe to bump to a version that will be supported going forward <!--- 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 #11276 Though this change doesn't result in guaranteed Python 3.11 support, it should allow users of Python 3.11 to at least install Pulumi successfully without Deprecation warnings etc. grpcio 1.4X does not ship 3.11-compatible wheels, so users are starting to see errors when installing Pulumi - bumping to this version also does not change our existing proto clients in Python, so feels like a relatively safe change. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] 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. --> 11437: Mark external modules as forign r=justinvp a=iwahbe Fixes #8070 Progress on #11427 Co-authored-by: Kyle Pitzen <kyle.pitzen@gmail.com> Co-authored-by: Ian Wahbe <ian@wahbe.com>
11440: Cleanup import generation r=iwahbe a=iwahbe Cleanup the `getPulumiImport` function. In doing so, remove an edge causing extraneous `/index` in #11427. For reviewers, looking at the diff for this PR is painful. It's much easier to review the old and new code separately. Part of #11427. Co-authored-by: Ian Wahbe <ian@wahbe.com>
11440: Cleanup import generation r=iwahbe a=iwahbe Cleanup the `getPulumiImport` function. In doing so, remove an edge causing extraneous `/index` in #11427. For reviewers, looking at the diff for this PR is painful. It's much easier to review the old and new code separately. Part of #11427. Co-authored-by: Ian Wahbe <ian@wahbe.com>
11440: Cleanup import generation r=iwahbe a=iwahbe Cleanup the `getPulumiImport` function. In doing so, remove an edge causing extraneous `/index` in #11427. For reviewers, looking at the diff for this PR is painful. It's much easier to review the old and new code separately. Part of #11427. Co-authored-by: Ian Wahbe <ian@wahbe.com>
As each of the underlying problems were fixed, we can now close the issue. |
Creating the default
pulumi new serverless-aws-yaml
and thenpulumi convert --language go --out ./go
fails with this:The code it generates is also wrong in referencing
github.com/pulumi/pulumi-aws-apigateway/sdk/apigateway/index
and in using unqualified references to types fromapigateway
likeRouteArgs
.The YAML source code from the default template is this:
The text was updated successfully, but these errors were encountered: