This message was deleted.

sparse-intern-71089

04/27/2023, 3:15 PM

This message was deleted.

billowy-army-68599

04/27/2023, 4:14 PM

i believe this is expected behaviour, if you modify the block device size it triggers a replacement. if you want to resize the device, you’ll need to do it manually

red-flower-37420

04/27/2023, 4:20 PM

Hmm - do you know why that is? Since the volume can be resized from the console, I expected to be able to do the same with Pulumi.

billowy-army-68599

04/27/2023, 4:24 PM

because it’s defined inline in the ec2 instance, if you define it with this resource you can resize it https://www.pulumi.com/registry/packages/aws/api-docs/ebs/volume/

red-flower-37420

04/27/2023, 4:26 PM

Gotcha yeah I was just thinking of the ebs.Volume approach.I think that'll work for us fine for normal instances, but I can't use that when the instance comes with multiple volumes that come over from the AMI.

red-flower-37420

04/27/2023, 4:27 PM

To do it in code, I guess I could use get_volume to retrieve the volume info and then use botocore to increase the volume's size. But... if that's the case, why can't Pulumi do the same?

13 Views

Open in Slack

Previous Next

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.