I'm using Pulumi on GCP, and I'd like to specify a bash script that would run just once after the VM is created. I saw that compute.Instance has the parameter metadata_startup_script, but IIUC it will run each time the machine boots.
Add a comment
|
2 Answers
Indeed, metadata_startup_script runs every time the machine boots, but you can add set an environment variable (maybe something inside .bashrc like $INIT_RUN=1) the first time you run it, and skip running it when the variable is already set.
1 Comment
dimid
Thanks, but I'm looking for a pulumi-native method, e.g. some post-create hook, and not bash-based solutions.
The metadata_startup_script in your Compute Engine runs every time the instance boots. But if you want to specify a bash script that would run just once after the VM is created. For this you can use startup scripts with a flag file or cloud -init.
You can use the metadata_startup_script but add logic in the script to check the existence of a flag file. If the flag file exists, the script does nothing immediately. If the flag file doesn’t exist, execute the script and then create the flag file.
Cloud-init is also a very helpful tool for this purpose. Which provides more advanced configuration options for your instances, including running scripts only once.
3 Comments
Sai Chandini Routhu
Refer to this Stack link and Serverfault link may helpful to resolve your issue.
dimid
Could you provide a minimal example with pulumi and cloud init?
Sai Chandini Routhu
@dimid To use Cloud-init in pulumi. you need to provide a cloud-init script as metadata when creating a vm. which helps to run only once during the VM first boot. Refer to this Github link and Cloud-init documentation by Nathaniel Stickman for more information.