Regarding comment from manuel (boillodmanuel): I feel I'm one of the 95% of users where write_files would be very useful to occur after the users module.
Currently, my work-around is:
runcmd:
- cloud-init single --name write_files --frequency once
...which runs over the same files created before, but now applies the correct permissions, at least on an EC2 with Amazon Linux 2.
My question is, as this bug is still "open" is there an official work-around?
Hi,
Regarding comment from manuel (boillodmanuel): I feel I'm one of the 95% of users where write_files would be very useful to occur after the users module.
Currently, my work-around is:
runcmd:
- cloud-init single --name write_files --frequency once
...which runs over the same files created before, but now applies the correct permissions, at least on an EC2 with Amazon Linux 2.
My question is, as this bug is still "open" is there an official work-around?