VergeIO Plugin Community Integration Request

[dzarzycki]

Description

A comprehensive Packer plugin for creating virtual machines images on VergeIO virtualization platform

https://github.com/verge-io/packer-plugin-vergeio

Integration Tier

Community Integration

Checklist

• Has valid metadata.hcl file in plugin repository.
• Has added integration scripts packer-plugin-scaffolding to plugin repository.
• Has added top-level integration README.md file to plugin docs directory.
• All plugins components have one README.md describing their usage.
• Has a fully synced .web-docs directory ready for publishing to the integrations portal.

[dzarzycki]

Referencing other recent closed PRs for community integrations, it appears that something needs to be completed upstream before I am able to trigger integration notification actions tag/manual without errors. Please advise if further information is required. We drifted a little bit away from Packer Scaffolding but on my review it appears in order to proceed and we are ready for release. Thank you.

[tanmay-hc]

Hi @dzarzycki
I've added the Nebius plugin to our Integrations page. However, there seems to be some technical issue from our side and the plugin is not showing up on the page.
Can you manually trigger the notify-integrations-release-via-manual workflow dispatch? That should make the plugin visible.
Let me know if you encounter any error during the workflow.

[dzarzycki]

Hi @tanmay-hc — I triggered the notify-integration-release-via-manual workflow as requested (version 0.1.1, branch main). The workflow runs and the metadata validates, but the final notify call fails with Failed to notify release: API responded with [500].

Failed run for reference: https://github.com/verge-io/packer-plugin-vergeio/actions/runs/27435290685

Since this is a server-side error, could you check the backend logs for the packer/verge-io/vergeio registration? Happy to re-trigger once you've had a look.

[dzarzycki]

Update: we found and fixed a layout issue on our side — component READMEs weren't at components/<type>/<slug>/README.md, so the builder, provisioner, and post-processor components were being submitted with readme: null. That's fixed; the payload now validates with all five component docs populated. The API still responds 500: https://github.com/verge-io/packer-plugin-vergeio/actions/runs/27436363678 — so the remaining issue does appear to be on your side.