https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
j
If by “bare metal” you mean a normal VM like an EC2 in AWS there’s a guide here https://pulumi.io/quickstart/aws/tutorial-ec2-webserver/
There are also equivalent guides for other supported cloud platforms
b
@jolly-egg-4894 thanks ! How does pulumi cope with locking resources ? In terraform there is a (remote) state. What about pulumi ?
j
Remote state was recently added to Pulumi. There’s a PR in the works adding locking to remote state files: https://github.com/pulumi/pulumi/pull/2697
I believe this is the PR that initially added remote state files https://github.com/pulumi/pulumi/pull/2455
b
so how did it work so far when the whole team has been modifying different part of infrastructure ?
j
I’ve not used Pulumi in a production project myself but before remote state I guess it would have been a case of having a script to download and upload the state to your CI & CD Pipeline. Right now I guess you could have a dynamodb table where you toggle a value as locked before running pulumi & then put it back to unlocked after
Not sure what the recommended method is atm
I guess instead of the old dynamo method your script could actually use s3's locking capabilities like pulumi will in the future https://aws.amazon.com/about-aws/whats-new/2018/11/s3-object-lock/
🤷
m
By default, Pulumi uses its own hosted platform to manage state: https://pulumi.io/reference/state/ https://pulumi.io/reference/service/
You can choose not to use that, though, by working locally (a la Terraform) or by using an alternate backend, as mentioned above.
s
Note that object locks are NOT what they sound like
And are not useful for that
Open in Slack
PreviousNext
Powered by