AllowedUses lists the settings in camel case when legal values are snake case. #151
Description
What happened?
AllowedUses lists the settings in camel case when legal values are snake case for both typescript and go sdk. Python looks to be fine. It looks like the comment is also getting updated incorrectly:
// List of key usages allowed for the issued certificate. Values are defined in [RFC 5280](https://datatracker.ietf.org/doc/html/rfc5280) and combine flags defined by both [Key Usages](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.3) and [Extended Key Usages](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.12). Accepted values: `anyExtended`, `certSigning`, `clientAuth`, `codeSigning`, `contentCommitment`, `crlSigning`, `dataEncipherment`, `decipherOnly`, `digitalSignature`, `emailProtection`, `encipherOnly`, `ipsecEndSystem`, `ipsecTunnel`, `ipsecUser`, `keyAgreement`, `keyEncipherment`, `microsoftCommercialCodeSigning`, `microsoftKernelCodeSigning`, `microsoftServerGatedCrypto`, `netscapeServerGatedCrypto`, `ocspSigning`, `serverAuth`, `timestamping`.
What works is:
AllowedUses: pulumi.StringArray{
pulumi.String("server_auth"),
},
Steps to reproduce
They are verified wrong here:
https://github.com/pulumi/pulumi-tls/blob/master/sdk/nodejs/locallySignedCert.ts#L36
Expected Behavior
They should still be in snake case.
Actual Behavior
You get a warning that it will be ignored.
Output of pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).