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
Lack of provider method/field in class besom.api.eks.Cluster #397
Comments
Thank you for the report, I confirm we lack this method currently. The workaround in this case is to explicitly create a provider like in this example. @lbialy we need to find a good API design, because I'd like to avoid the problems other SDKs have with having both From TS API:
Relevant documentation and code:
|
First of all, is cluster.provider a field on the resource or a core method exposing provider used to deploy this particular resource? I assume the latter and that in other implementations it's just a method inherited from Resource, right? If so, it should be trivial to add it in core. All it has to do is to reach to the guts of context and fetch the provider from the state. The issue is - there's a probability that field |
@pawelprazak your opinion here? |
It's tricky IMO to provide sensible semantics here, because:
This has some consequences that are less than ideal:
More context here: pulumi/pulumi#8796 I believe Scala has strong enough type system to handle this gracefully, but I'm yet to find an elegant solution. Alternatively, maybe the upstream implementation is good-enough and I'm overthinking this.
I'm curious what would StackResource return, I assume a |
You're thinking in terms of inheritance. We are free to ditch inheritance whenever we want to! This. is. Scala! We almost never upcast to
|
When I ask pulumi AI "aws eks hello world” I get:
https://www.pulumi.com/ai/conversations/6ff221c6-9b0b-49be-8233-1afaf3e7fea7
I want to use
in Besom. Like below:
But class besom.api.eks.Cluster don't have a provider method.
The text was updated successfully, but these errors were encountered: