Avoid using 'safefile'

[juan131]

Signed-off-by: juan131 juan@bitnami.com

This PR fixes the issue described below when running ini-file with an unprivileged user:

---

When we have a “non-root” container run as 1001:root and we have a file with the permissions below:

-rw-rw-r-- 1 root root 22338 Apr  7 15:56 default.ini

The user can write in the file since it belongs to the root group. However, running the command below will fail:

./ini-file set --section section --key foo --value bar default.ini

The reason is how ini-file perform write operations. It's using safefile that create a temporal file, to replace the destination file with this temporal file later. This temporal file is created with -rw-r-r-- 1001:root permissions, which is wrong for two reasons:

• It's not respecting the original ownership
• It's not respecting the original permissions.

We tried to fix this by running some chown/chmod operations but it's not working since "chown" operations require privilege permissions.

---

Solution: stop using safefile and directly write in the destination.

[marcosbc]

LGTM