Differences in the generated SDK between current code gen and the schema-based code gen #1072
Labels
kind/bug
Some behavior is incorrect or out of spec
mro1
Monica's list of 1st tier overlay related issues
resolution/fixed
This issue was fixed
While working on the resource docs, I noted a few issues with the schema based code gen when using it to generate the type strings from the k8s Pulumi schema.
NodeJS
s3
module'sBucketArgs
for nodejs. And here's the input args type forControllerRevision
in k8s.C#
Namespaces
override map uses the normalized k8s module names rather than the actual module names as the key in the map. This makes it so that every lookup in the map using the raw module name will be a miss.Pulumi.Kubernetes.Types.Inputs.<ModuleName>.<PropertyType>
(andTypes.Outputs
for output types) whereas the schema code gen will generatePulumi.Kubernetes.<ModuleName>.Inputs.<PropertyType>
. Note the placement of the input/output qualifier in the namespace path.Overlays
This is sort of a duplication of what I mentioned above under the NodeJS heading. But this one is a problem in both NodeJS, as well as C#.
The input type for the overlay resource is in the same namespace as the resource, which is actually correct, however, the type name does not follow the naming convention used by non-overlay resource input types. Specifically, these input types don't have the suffix "Args". For example, the input param for the
Chart
resource isChartOpts
orLocalChartOpts
, instead ofChartArgs
.The text was updated successfully, but these errors were encountered: