Skip to content
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

maxSnapshots #11139

Closed
Man-Yee opened this issue Jul 9, 2021 · 3 comments
Closed

maxSnapshots #11139

Man-Yee opened this issue Jul 9, 2021 · 3 comments

Comments

@Man-Yee
Copy link

Man-Yee commented Jul 9, 2021

Issues on GitHub are intended to be related to bugs or feature requests, so we
recommend using our other community resources instead of asking here if you
have a question.

@Man-Yee
Copy link
Author

Man-Yee commented Jul 9, 2021

Hi,

I would like to disable snapshot in vmware.
I know that I can set this advanced configuration (snapshot.maxSnapshots) to "0" to achieve this.
I also know that if I modify the .ovf file with the following line, it will achieve the wanted result:
<VirtualHardwareSection ovf:transport="com.vmware.guestInfo"> <Info>Virtual hardware requirements</Info> . . . <vmw:ExtraConfig ovf:required="false" vmw:key="snapshot.maxSnapshots" vmw:value="0"/> </VirtualHardwareSection>

I would like to automate this. According to documentation, I can possibly use extraConfig in configure_parameters.
I tried many variations in my .hcl file , but without success:

configuration_parameters = { extraConfig = { key = "snapshot.maxSnapshots" value = "0" } }

It complains about
Inappropriate value for attribute "configuration_parameters": element "extraConfig": string required.

Then I tried this:
configuration_parameters = { "extraConfig" = "snapshot.maxSnapshots=0" }
Although the build pass, deploying the .ova file does not yield the wanted result.

What is the correct format to use extraConfig? Is snapshot.maxSnapshots supported?

@github-actions
Copy link

This issue has been migrated to hashicorp/packer-plugin-vmware#32 due to the Packer Plugin split.

Please follow the new issue for updates.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants