With the IaC approach, you simply modify the original script to add/change/remove resources, and commit the script to your shared code repository. Let's put this into practice. Suppose you want to change the name of the collaborator from Alice to Maria. To do this, simply change the property of workerOne in the code: JavaScript Copy the code ... const workerOne = new Resource('worker-one', { resource: ['taskrouter', { workspaces: workspace.sid }, 'workers'], attributes: { // friendlyName: 'Alice', friendlyName: 'Maria', attributes: JSON.stringify({ languages: ['en', 'es'] }), }, }); … If you run the deploy command again, you will see the following: Bash Copy the code telegram philippines girl Previewing update (dev): Type Name Plan Info pulumi:pulumi:Stack my-first-iac-project-dev ~ └─ pulumi-nodejs:dynamic:Resource worker-one update [diff: ~attributes] Resources: ~ 1 to update 6 unchanged This means that a resource ("worker-one") will be updated because one of the elements ( attributes) has changed since the last deployment.

Select yes and press Enter. You will see the following: Bash Copy the code Updating (dev): Type Name Status Info pulumi:pulumi:Stack my-first-iac-project-dev ~ └─ pulumi-nodejs:dynamic:Resource worker-one updated [diff: ~attributes] Resources: ~ 1 updated 6 unchanged As you can see in the command output, Pulumi detected a change in worker-one and modified the deployed resource accordingly. If you navigate to the TaskRouter Workspaces page in the Twilio console, you will see that the collaborator name has changed: TaskRouter Collaborators Updated To make sure all other devs update their workspace, you need to distribute (e.g. commit the file to a shared directory) the new configuration file ( index.