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.

Pulumi Community

image.png

I would need some help with this piece.

The same thing works in terraform in first attempt but I am not sure I am getting error even though the args is mentioned in the docs(`screenshot attached`)

<@U02JMLLU6TF> - that argument was only added recently to the tf provider, we'll get the rancher2 provider updated for you

ohh……. I didn’t knew about it.

<@UCWG26BH7> I understand now. No worries.

Is there a need to open a ticket/issue something on github?

Can you please add me to the update

github username:  `prashant0085`

<@U02JMLLU6TF> looks like we;ve done that update. what version of the provider are you using?

```devops-rancher-next@ /Users/prashanttiwari/zondax/devops-rancher-next
├── @pulumi/cloudinit@1.1.0
├── @pulumi/hcloud@1.5.0
├── @pulumi/pulumi@3.13.2
├── @pulumi/rancher2@3.3.0
├── @types/node@10.17.60
├── @typescript-eslint/eslint-plugin@4.33.0
├── @typescript-eslint/parser@4.33.0
├── eslint@7.32.0
├── fs@0.0.1-security
├── tslint@6.1.3
└── typescript@4.4.3```

ok…probably it didn’t updated due package-lock file with older npm.

This is me using pulumi as well as typescript first time :sweat_smile:

Is it recommended to keep all packages to `latest?`

no, that could introduce changes you don't expect. if you need a feature, update it when you need