This message was deleted.
# general
s
This message was deleted.
l
Why is the
metadata
member of the
BackendConfig
class generated like this?
Copy code
public readonly metadata!: pulumi.Output<ObjectMeta | undefined>;
Looking at e.g. the Kubernetes
Service
class, the
metadata
member is this:
Copy code
public readonly metadata!: pulumi.Output<outputs.meta.v1.ObjectMeta>;
If I drop the
undefined
from the generated type definition, my code works correctly. Should I file a Github issue for this?
g
Yes, that seems like a bug. Every k8s resource will include a
.metadata
field, so
| undefined
doesn’t make sense.
👍🏼 1
l