echoing-dinner-19531
07/14/2022, 3:26 PMbrainy-church-78120
07/14/2022, 3:28 PMwhite-chef-55657
07/18/2022, 11:57 AMwhite-chef-55657
07/18/2022, 11:58 AMbig-architect-71258
07/21/2022, 7:29 AMdelightful-salesclerk-16161
delightful-bear-69098
08/12/2022, 9:52 AMdelightful-bear-69098
08/15/2022, 8:46 AMlimited-rainbow-51650
08/22/2022, 1:22 PMbillowy-army-68599
limited-rainbow-51650
08/23/2022, 9:45 AMelegant-window-55250
08/23/2022, 9:45 AMlimited-rainbow-51650
08/23/2022, 12:12 PMGH repo <- GH team <- GH member
I changed this and now added everyone directly:
GH repo <- GH member
with the same permissions. So although you were removed from the team, you were added again directly. Too bad all those Github email notifications are sent out which might confuse you. 🙏🏼limited-rainbow-51650
08/23/2022, 4:12 PMbig-architect-71258
08/25/2022, 1:10 PMacoustic-tiger-77630
08/25/2022, 7:59 PMprovider/resources.go
In the Golang section below, I see the url pointing to the pulumi repository instead of the provider repo. Which one is correct?
Golang: &tfbridge.GolangInfo{
ImportBasePath: filepath.Join(
fmt.Sprintf("<http://github.com/pulumi/pulumi-%[1]s/sdk/|github.com/pulumi/pulumi-%[1]s/sdk/>", mainPkg),
tfbridge.GetModuleMajorVersion(version.Version),
"go",
mainPkg,
),
GenerateResourceContainerTypes: true,
2. In provider/cmd/pulumi-resource-foo/main.go
it also points to a pulumi repository i.e zpa “http://github.com/pulumi/pulumi-xyz/provider” Should the repository still point to pulumi instead? Looking at other providers, they all point to pulumi instead of their own repo as specified in the boilerplate.limited-rainbow-51650
08/26/2022, 12:11 PMbig-architect-71258
08/26/2022, 12:14 PMbig-architect-71258
08/26/2022, 12:20 PMwide-cat-87818
08/26/2022, 12:32 PMlimited-rainbow-51650
08/26/2022, 2:27 PMlimited-rainbow-51650
08/29/2022, 8:35 AMdocs
folder of your time
provider is copied over for registry publishing. But on the registry side, there are linting failures. Can you fix these in the provider repo?
https://github.com/pulumi/registry/runs/8041632103?check_suite_focus=true#step:7:33big-architect-71258
08/29/2022, 8:37 AMlimited-rainbow-51650
08/29/2022, 8:43 AMbig-architect-71258
08/30/2022, 1:04 PMacoustic-tiger-77630
09/05/2022, 10:06 AM pulumi up master
Previewing update (zscaler/go_zpa_app_connector_group)
View Live: <https://app.pulumi.com/zscaler/go_zpa_app_connector_group/go_zpa_app_connector_group/previews/882288d9-8109-46a3-a2e7-b12fee77dfa2>
Type Name Plan Info
+ pulumi:pulumi:Stack go_zpa_app_connector_group-go_zpa_app_connector_group create
└─ pulumi:providers:zpa default 1 error
Diagnostics:
pulumi:providers:zpa (default):
error: could not read plugin [/Users/wguilherme/go/bin/pulumi-resource-zpa] stdout: EOF
many-telephone-49025
09/06/2022, 6:36 AMgreat-queen-39697
09/14/2022, 4:54 PMlimited-rainbow-51650
09/27/2022, 8:02 AMpulumi/registry
like this one:
https://github.com/pulumi/registry/pull/1030/filesmany-telephone-49025
09/28/2022, 12:40 PMHTTPError: 400 Bad Request from <https://upload.pypi.org/legacy/>