cluster.eksCluster is an Output and other resources too

[1oglop1]

Describe what happened

eksCluster property is an output and therefore cannot be made a parent, I think that resources should never be outputs unless there is no other way around it.
When resource is an output, it creates a nested Output<Output> which forces the user into an anti pattern of creating resources during apply.

https://github.com/pulumi/pulumi-eks/blame/385ec2a620e0bb83497bd970e68a82f41abfa022/nodejs/eks/cluster/cluster.ts#L2265

This is directly related to #1466, if resources weren't outputs, the workaround to use the cluster as a parent would be simple.

Sample program

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

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).

[rquitales]

@1oglop1 Thanks for flagging this. I want to highlight that if we decide to do this, it would require a major version upgrade in this provider as it'll be a breaking change.

I'm curious if there is a need to set cluster.eksCluster as a parent. Is it not sufficient to just set cluster to be a parent? If you can provide some code snippets to showcase the why this would be helpful, it'd help further this design decision.

[1oglop1]

@rquitales Setting ComponentResource as a parent is not a good idea; you can find out by following the link of the issue mentioned in the report. It sometime work, but something inside this component breaks.
pulumi/pulumi#18705

I've noticed one more "smaller" issue - accessEntires cannot handle Input and I need to query array of IAM roles, which leaves me with an Output or a Promise, and the only choice I seem to have is to move all the code of my component into protected async initialize()

In the past, I have had terrible experiences with AWSx and at the moment, I am judging the benefits of @pulumi/eks over building my own component resource.
Is there any write-up describing the benefits? I know that deploying eks without eksctl is a quite annoying task (I've burned myself ~6 years ago), but I wonder how far the Terraform module has come and what @pulumi/eks brings on top of it.

I do not mean to sound harsh; it's just that the lack of information and the justification of existing code make my architectural decisions harder.