-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to specify user_data in a template #267
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fernflower The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
8df8593
to
f2ad4b1
Compare
@mkumatag Could you please advise me on failing test https://github.com/ppc64le-cloud/packer-plugin-powervs/actions/runs/12869521195/job/35878518826?pr=267 ? I tried reproducing with |
https://github.com/ppc64le-cloud/packer-plugin-powervs/actions/runs/12869521195/job/35878518826?pr=267 giving all the errors you need to address |
It will be great if you can include the sample usage of this newly introduces field in the description above. |
f2ad4b1
to
9f9ede9
Compare
For some cases relying on a script to be passed to shell provisioner is not enough. So let's allow user to specify actual userdata to be passed to the vm on creation, this will help in complex scenarios like persistently changing network routing that will survive reboots. Sample configuration: "user_data": "#cloud-config\nbootcmd:\n- ip route add 10.0.0.0/8 via 10.130.68.1 dev eth0"
9f9ede9
to
559efbe
Compare
For some cases relying on a script to be passed to shell provisioner is not enough. So let's allow user to specify actual userdata to be passed to the vm on creation, this will help in complex scenarios like persistently changing network routing that will survive reboots.