-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Missing constructor syntax examples for the Pulumi service provider #16191
Comments
@Zaid-Ajaj, any idea why some of the languages show "Coming soon!" for constructor syntax examples? TS, Python, Go, C# are "Coming soon", but Java and YAML are filled-in. |
The intermediate PCL program generated for resource "teamStackPermissionResource" "pulumiservice:index:TeamStackPermission" {
organization = "string"
permission = "read"
project = "string"
stack = "string"
team = "string"
} Where Program-gen for C# fails here, generating a PANIC so this specific example is skipped: // Resource pulumiservice:index:TeamStackPermission
var teamStackPermissionResource = new PulumiService.TeamStackPermission("teamStackPermissionResource", new()
{
Organization = "string",
Permission = %!v(PANIC=Format method: Unsafe enum conversions from type string not implemented yet: "read"
=> enum(pulumiservice:index:TeamStackPermissionScope(number): cty.NumberIntVal(101),cty.NumberIntVal(102),cty.NumberIntVal(103))),
Project = "string",
Stack = "string",
Team = "string",
}); TypeScript, Go and Python all fail to a similar error. Fix incoming |
…meric enums as input (#16223) # Description Fixes #16191 The original issue is that the intermediate PCL we generate used enum names instead of enum values for numeric enum inputs. This PR changes it so that the PCL program now uses the first numeric value for the first enum case then subsequently fixing downstream program-gen bugs that didn't know how to handle numeric values as inputs for enums. ## Checklist - [ ] I have run `make tidy` to update any new dependencies - [x] I have run `make lint` to verify my code passes the lint check - [ ] I have formatted my code using `gofumpt` <!--- 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 Cloud, 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 Cloud API version <!-- @pulumi employees: If yes, you must submit corresponding changes in the service repo. -->
https://www.pulumi.com/registry/packages/pulumiservice/api-docs/teamstackpermission/
The text was updated successfully, but these errors were encountered: