Open ionut-maxim opened 2 years ago
Looking at how this is implemented right now it will always get an absolute path to the playbook https://github.com/hashicorp/packer-plugin-ansible/blob/536562fd497fc5049018ba90db705adc6b2c9634/provisioner/ansible/provisioner.go#L812
Maybe a new input can be added to the plugin where we can use as input a playbook that exists in a Galaxy collection. Example:
provisioner "ansible" { playbook = "namespace.collection.playbook" galaxy_file = "requirements.yml" }
I was going to create an issue, but I believe it is covered here. To confirm, this will allow the usage of Collection playbooks when implemented, correct?
Looking at how this is implemented right now it will always get an absolute path to the playbook https://github.com/hashicorp/packer-plugin-ansible/blob/536562fd497fc5049018ba90db705adc6b2c9634/provisioner/ansible/provisioner.go#L812
Maybe a new input can be added to the plugin where we can use as input a playbook that exists in a Galaxy collection. Example: