Allow Alloy to Create Config File directly from File

[aybrl-edu]

#284

I want to enhance the configuration setup for Alloy to either accept a direct file from downstream or, if no file is provided, fall back to the existing template mechanism that uses a variable.

Current Behavior

Currently, the config.alloy.j2 template is used to generate the /etc/alloy/config.alloy file, with the file content entirely dependent on the variable {{ alloy_config }} that holds the content from downstream

Requested Behavior

Add the ability to provide a file directly from downstream {{ alloy_config_file }}

If alloy_config_file is provided, copy this file directly to /etc/alloy/config.alloy.
If alloy_config_file is not provided, continue using the existing template mechanism with the variable to populate /etc/alloy/config.alloy.

[CLAassistant]

All committers have signed the CLA.

[gardar]

I don't think it's a good idea to add this to the role.

If you really want this then you can do it already with a lookup, or you can skip the configuration in the role and do this task in your playbook.

alloy_config: "{{ lookup('ansible.builtin.template', '/path/to/your/custom/template.j2') }}"
alloy_config: "{{ lookup('ansible.builtin.file', '/path/to/your/custom/config.file') }}"