https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
v
are you trying to access the output of something? you might need to use the 
apply
method to extract the value. https://www.pulumi.com/docs/intro/concepts/inputs-outputs/#apply
v
Thank you.
i think this is a bug in the 
@pulumi/eks
v
i think thats just a problem resolving a promise mate, i am using the eks library and its fine
what exactly are you trying to do, can you send code?
v
@victorious-church-57397 sure. here it is https://termbin.com/tz98
it seems to work fine when cluster creates. the problem happens when i rerun the 
up
command
Copy code
❯ pulumi up --yes
Previewing update (dev)

View Live: <https://app.pulumi.com/k1ng440/allrites-infrastructure/dev/previews/bf553031-8e0a-4dd0-8f6f-94e64a4aff55>

     Type                                   Name                                Plan        Info
     pulumi:pulumi:Stack                    allrites-infrastructure-dev                     1 error
     └─ custom:resource:eks                 primary-eks
        └─ eks:index:Cluster                primary-eks-eks-cluster
 ~         ├─ aws:eks:Cluster               primary-eks-eks-cluster-eksCluster  update      [diff: ~vpcConfig]
 ~         ├─ eks:index:VpcCni              primary-eks-eks-cluster-vpc-cni     update      [diff: ~kubeconfig]
 +-        ├─ pulumi:providers:kubernetes   primary-eks-eks-cluster-eks-k8s     replace     [diff: ~kubeconfig]
 +-        └─ kubernetes:core/v1:ConfigMap  primary-eks-eks-cluster-nodeAccess  replace     [diff: ~metadata,provider

Diagnostics:
  pulumi:pulumi:Stack (allrites-infrastructure-dev):
    error: Running program '/home/k1ng/projects/allrites-infra' failed with an unhandled exception:
    TypeError: Cannot read properties of null (reading 'data')
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/nodegroup.ts:501:95
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/output.ts:383:31
        at Generator.next (<anonymous>)
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:21:71
        at new Promise (<anonymous>)
        at __awaiter (/home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:17:12)
        at applyHelperAsync (/home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:229:12)
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/output.ts:302:65
        at processTicksAndRejections (node:internal/process/task_queues:95:5)
@victorious-church-57397
v
sorry mate im working atm, havent got time to look just yet, will take a look later if i can
👍 1
e
Looks like the eks clusters certificateAuthority isn't being set correctly, probably not a bug in the eks library but the aws package itself.
Also a note, code like 
.apply(name => name)
is pointless. That's just the same as not calling apply at all.
👍 1
Does this work if you create a fresh stack, and run up twice? Once to actually create it, then again which should do nothing.
v
Yes its works fine on fresh stack. running up again causes this problem
Also i have no idea why the vpcConfig is changing on rerunning the 
up
command
Copy code
aws:eks:Cluster               primary-eks-eks-cluster-eksCluster  update      [diff: ~vpcConfig]
If you like, i can give you access to the repo
e
Well no good giving it to me, aws and eks aren't my teams projects 🙂 but do raise an issue on the eks or aws github repos and let them know you've got a repro you can share
120 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by