Sorry for the long wait, after taking a closer look at the issue and the documentation again, it’s not a problem with your template or the code for Packer, but it is as you first pointed out an incompatibility for the Openstack builder.
For artifacts to be able to push data to HCP, they need to be compatible, as highlighted in the documentation: HCP Packer Support | Packer | HashiCorp Developer.
Right now, the Openstack builder does not do that, hence the incompatiblity. Sorry for not pointing this out earlier.
If supporting HCP Packer is what we want here, we need to implement that for the builder’s Artifact. To be frank, we don’t have an Openstack installation on which to test it, so it’ll be hard for us to understand the kind of data would be relevant to add to the HCP artifact, so will be testing.
Because of this, would it be possible for you to add this to the Openstack builder? We can assist as much as is needed, and we’ll of course review the code and release the plugin when it’s in a satisfactory state.
For reference, here’s the documentation for the image package that defines the expected structure: image package - github.com/hashicorp/packer-plugin-sdk/packer/registry/image - Go Packages
And for an implementation example, I find the
amazon-ebsvolume easy to understand and take inspiration from: packer-plugin-amazon/artifact.go at main · hashicorp/packer-plugin-amazon · GitHub
Please let me know what your thoughts are, and what kind of help we can provide to help guide you on this track, should you wish to give a try at the implementation.
Apologies again for taking our time answering this question, hopefully we’ll reach a satisfactory conclusion for everyone on this.