Allow all extra config when exporting to content library

[herkalurk]

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Based on the documentation I can see, I cannot export a VM from inventory to a content library including the extra config

Use Case(s)

We are needing to ensure some advanced configuration properties flow from the automated vm template creation to final vm deployment in ESXI/vCenter environments

Potential Configuration

Unsure, based on the allowed configuration settings when exporting a finished template to the content library, this Boolean isn't selectable, but is available in the vcenter UI when cloning a VM to OVF in the content library

References

https://github.com/vmware/packer-plugin-vsphere/blob/v1.4.2/builder/vsphere/common/step_import_to_content_library.hcl2spec.go

[tenthirtyam]

Have you used ovf_flags?

    content_library_destination {
            library = "Example Content Library"
            ovf = true
            ovf_flags = ["EXTRA_CONFIG"]
    }

Ref:

packer-plugin-vsphere/builder/vsphere/common/step_import_to_content_library.go

Lines 79 to 82 in 68f84bd

	// Flags to use for OVF package creation. The supported flags can be
	// obtained using ExportFlag.list. If unset, no flags will be used.
	// Known values: `EXTRA_CONFIG`, `PRESERVE_MAC`.
	OvfFlags []string `mapstructure:"ovf_flags"`