Metadata startup scirpt

[Andreas Potamitis]

Hello community.

I am trying to deploy a google compute engine using terraform. The instance is created successfully but I am having issues deploying metadata startup scripts. 

I checked permissions, syntax based on documentation and using windows-startup-script-ps1 = "basic powershell commands" it seems that the commands are not executed at all.

Checked the logs in port 1 and during checks, it does not even identify that there are metadata to be executed during the instance deployment.

Also, the metadata script is visible on the instance information panel, on the bottom.

Any help appreciated.

Thank you.

[Prakash Shanmugam]

Hi Andreas Potamitis

As per google documentation, "windows-startup-script-ps1" will be executed after each time of initial boot. If you want the scripts to be executed at initial boot, you need to change the startup script key as "sysprep-specialize-script-ps1". 

You can refer the complete documentation about the order of startup script execution for windows at https://cloud.google.com/compute/docs/instances/startup-scripts/windows#order_of_execution_of_windows_startup_scripts.

Let me know if this helps to get resolved your issue.  

[Digil (Google Cloud Platform Support)]

Hello Andreas,

As explained by the other community support person, I believe you have to use the 'sysprep_specialize-script-ps1' as the metadata key for the startup script to get it executed during the time-of initial booting of the GCE VM.

Before testing it by using your 'Terraform environment', I would also recommend you to test the scenario by passing the startup script directly (OR from a local file OR from a Cloud Storage) to see if it is executing properly. If it is providing the expected result, then you might need to get in touch with the Terraform's support channel for an additional review of your code. If it is not providing an expected result, then I would strongly recommend you to report it as a defect(bug) using the Google Cloud Platform's issue-tracker report channel. While opening the issue-tracker report, try to include as many details, such as reproduction steps, documents you were following, etc.

[Yaqub Omofoyewa]

Hello Andreas,

 I am trying to get something right here about what you mean by "but I am having issues deploying metadata startup scripts." Attaching a metadata script is an automated startup script that you do not have to interfere with whenever you are using Terraform on GCP. 

It will be attached to your resource "google_cloud_instance" code. In addition, it is expected to be like this  metadata_startup_script = "echo hi > /test.txt"

  

More informations about Terraform metadata startup script for compute engine can be found here:

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance#metadata_startup_script

Best regards

Yaqub

--
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/874b9fdd-4bf9-4d5d-a606-f2ab0df6bbafn%40googlegroups.com.