You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin is maintained by osbuild community which is backed by Red Hat. The osbuild tool, also known as image-builder, is shipped in Red Hat Enterprise Linux. The osbuild GH org is controlled by Red Hat employees and meets the company security standards (2FA). Both mentioned tools are currently upstream-only emerging tech that will be eventually integrated into Fedora and Red Hat Enterprise Linux. Therefore, community integration tier is fine.
Has added top-level integration README.md file to plugin docs directory. - docs are not generated
All plugins components have one README.md describing their usage.
Has a fully synced .web-docs directory ready for publishing to the integrations portal.
I am shooting in the dark here, but since the plugin is so simple, we would like to maintain the plugin documentation manually, thus there is no docs/ folder and no generation of .web-docs/ is going on at the moment. I hope this is fine and it will work, let me know otherwise and we can change it.
The text was updated successfully, but these errors were encountered:
Description
HashiCorp Packer plugin for image-builder-cli and bootc-image-builder. Builds are done on a remote linux machine over SSH.
The plugins is available at: https://github.com/osbuild/packer-plugin-image-builder
Integration Tier
This plugin is maintained by osbuild community which is backed by Red Hat. The osbuild tool, also known as image-builder, is shipped in Red Hat Enterprise Linux. The osbuild GH org is controlled by Red Hat employees and meets the company security standards (2FA). Both mentioned tools are currently upstream-only emerging tech that will be eventually integrated into Fedora and Red Hat Enterprise Linux. Therefore, community integration tier is fine.
Checklist
metadata.hcl
file in plugin repository.docs
directory. - docs are not generated.web-docs
directory ready for publishing to the integrations portal.I am shooting in the dark here, but since the plugin is so simple, we would like to maintain the plugin documentation manually, thus there is no
docs/
folder and no generation of.web-docs/
is going on at the moment. I hope this is fine and it will work, let me know otherwise and we can change it.The text was updated successfully, but these errors were encountered: