[Feature request] import blank/nonexistent files #1815

Is your feature request related to a problem? Please describe.

I want to set Anubis policies such that I can specify one file that applies to all machines, but have host-specific config files as well.

If I "- import" a file that doesn't exist, it fails. If I import a file that has no contents, it fails. I was hoping I could tell Puppet to create a blank file on all hosts that I could manually edit or deploy via some other method.

Solution you would like.

I should be able to specify a directory for import, or for policies, for instance:

POLICY_FNAME=/etc/techaro-botstopper/botPolicies.d

that can contain a list of policies that I can manage. Such a botPolicies.d directory could contain, eg,

00-header.yaml
01-HOSTNAME.yaml
02-APPSPECIFIC.yaml
03-catchall.yaml

This would also allow the anubis package to specify defaults (in the header, say) that users could override, and reinstalling the package would not overwrite user-specified policies.

Describe alternatives you have considered.

No response

Additional context

No response