Custom startup scripts #40
Comments
|
Sure thing, I’ll add this soon. ETA end of the week, early next at the latest. |
jeffmccune
added a commit
that referenced
this issue
Jan 13, 2021
This patch adds an input variable to allow an user defined startup script to execute immediately after the multinic startup script executes. The script must be bash and is stored in the startup-script-user instance metadata key.
3 tasks
jeffmccune
added a commit
that referenced
this issue
Jan 13, 2021
This patch adds an input variable to allow an user defined startup script to execute immediately after the multinic startup script executes. The script must be bash and is stored in the startup-script-user instance metadata key.
jeffmccune
added a commit
that referenced
this issue
Jan 13, 2021
This patch adds an input variable to allow an user defined startup script to execute immediately after the multinic startup script executes. The script must be bash and is stored in the startup-script-user instance metadata key.
jeffmccune
added a commit
that referenced
this issue
Jan 13, 2021
This patch adds an input variable to allow an user defined startup script to execute immediately after the multinic startup script executes. The script must be bash and is stored in the startup-script-user instance metadata key.
3 tasks
jeffmccune
added a commit
that referenced
this issue
Jan 13, 2021
(#40) Add startup_script_user input variable
jeffmccune
added a commit
that referenced
this issue
Jan 14, 2021
v2.1.0 - 2021-01-13 === * Add `startup_script` input variable to specify a bash startup-script to execute after routing is initialized. ([#40][issue40]) * tag '2.1.0': Update CHANGELOG for 2.1.0 (#40) Add startup_script_user input variable Add variable project_id for endpoints Add variable project_id for examples
jeffmccune
added a commit
that referenced
this issue
Jan 14, 2021
v2.1.0 - 2021-01-13 === * Add `startup_script` input variable to specify a bash startup-script to execute after routing is initialized. ([#40][issue40]) * tag '2.1.0': Update CHANGELOG for 2.1.0 (#40) Add startup_script_user input variable Add variable project_id for endpoints Add variable project_id for examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would it be possible to support a custom startup script that would run after the default routing startup and configuration scripts?
This could be used with the image_project/image_name parameters to use a custom centos-8 based image and configure additional monitoring, security, etc. in the running VMs. In our case, we would like to configure monitoring on the VMs.
The text was updated successfully, but these errors were encountered: