It seems cloud-init expects there to be a folder with meta-data and user-data files per provisioned host, Foreman does not seem to have such endpoints, and puts cloud-init files in the normal unattended path. How do I tell Foreman to put the meta-data and user-data files in the correct location?
I am on version 3.2 with the builtin cloud-init support, and am not using the old plugin.
As I understand it Foreman places all templates at a URL like this:
But cloud-init expects:
https://<hostname>/<path>/<install-hostname>/ (with a cloud-init file in that folder)