ZSphere / ZSvirt Packer Plugin Integration Request #13725

Description

Please register the ZSphere / ZSvirt Packer plugin as a Packer integration.

Repository: https://github.com/ZSvirt/packer-plugin-zsvirty
Release: https://github.com/ZSvirt/packer-plugin-zsvirty/releases/tag/v0.1.0

The plugin creates custom root-volume images on ZSphere / ZSvirt using three builders:

• zsvirt: provision a VM from an existing image and create a root-volume template.
• zsvirt-iso: perform an unattended operating-system installation from ISO, provision the guest, and create a root-volume template.
• zsvirt-snapshot: create an image from an existing root-volume snapshot.

It supports account and access-key authentication, SSH/WinRM provisioning, image export, and cleanup of temporary resources.

Plugin source: github.com/ZSvirt/zsvirty
Integration identifier: packer/ZSvirt/zsvirty
License: MPL-2.0

Integration metadata:
https://github.com/ZSvirt/packer-plugin-zsvirty/blob/main/.web-docs/metadata.hcl

Generated documentation:
https://github.com/ZSvirt/packer-plugin-zsvirty/tree/main/.web-docs

Version v0.1.0 has been published with platform binaries, SHA256 checksums, and a GPG signature. Remote installation using packer init and template validation for all three builders have passed with Packer 1.16.1.

The integration notification workflow currently reports:
Organization not found for integration identifier: 'packer/ZSvirt/zsvirty'

Please onboard the organization and integration, or advise if a different integration identifier is required.

This request replaces #13724 and is being submitted through the Plugin Integration Request template.

Integration Tier

Community.

Checklist

• Has valid metadata.hcl file in plugin repository.
• Has added integration scripts from packer-plugin-scaffolding to plugin repository, including documentation generation and manual/tag notification workflows.
• Has added top-level integration README.md file to plugin docs directory.
• All plugin components have one README.md describing their usage.
• Has a fully synced .web-docs directory ready for publishing to the integrations portal.