There is a request to have this run on Arm based macs.
This will need to be done in two parts:
This issue is to cover getting the Hosts.rb in the Core Provisioner:
We will need to look at using the vagrant plugin: vagrant-utm Wiki here: https://naveenrajm7.github.io/vagrant_utm/
To support using UTM, which uses QEMU as the hypervisor, minimal work need need to be done in order to create an appropriate packer template for this (as a x86 based template will work out of the box with UTM).
Once the Vagrant provisioner is ready for Arm based deployments, we can then move on to exposing a toggle in SHI, or a detection feature that if on Arm, and on Mac, us vagrant-utm instead of vagrant-virtualbox as the provider. This will involve changes to custom provisioners provisioner.yml, and for the two static provisioners, hcl_domino_standalone_provisioner and hcl_domino_additional_provisioner Hosts.template.yml
There is a request to have this run on Arm based macs.
This will need to be done in two parts:
This issue is to cover getting the Hosts.rb in the Core Provisioner:
We will need to look at using the vagrant plugin: vagrant-utm Wiki here: https://naveenrajm7.github.io/vagrant_utm/
To support using UTM, which uses QEMU as the hypervisor, minimal work need need to be done in order to create an appropriate packer template for this (as a x86 based template will work out of the box with UTM).
Once the Vagrant provisioner is ready for Arm based deployments, we can then move on to exposing a toggle in SHI, or a detection feature that if on Arm, and on Mac, us vagrant-utm instead of vagrant-virtualbox as the provider. This will involve changes to custom provisioners provisioner.yml, and for the two static provisioners, hcl_domino_standalone_provisioner and hcl_domino_additional_provisioner Hosts.template.yml