[UX]: Locked env variables should be "unlock-able"

[mimamuh]

Error Message and Logs

I've tried the "lock" feature of a environment variable and then tried to undo it.

Based on this ticket (#2697) the current "process" is actually "a feature". The process, to basically "undo" the lock again, is:

1. I have to delete the environment variable from the docker-compose config.
2. Then I have to delete it in the UI
3. I have to re-create it

Suggestion for a better workflow:

a) Either warn the user as soon as he clicks the "lock" button in a modal that this can't be un-done and that the only way to revert it, is to follow the cumbersome quirky process explained before. By explaining the process, it should already become clear, that this is not a well thought out process.

b) Or follow an improved UX by allowing the user to always undo his actions:

1. Allow the user to click the lock-icon to guide him through the "unlock" process
2. Based on the purpose of this lock feature (It is actually not obvious to me what the lock feature is meant for. Is it a security feature to protect team-mates from seeing the value? Or is it a protection feature to protect against accidental changes?):

• Just basic change protection: Show a modal and ask the user if he wants to remove the protection -> Cancel / Disable protection? Done!
• Permission/security feature: Allow to unlock by entering the user account password if the user has permission to do so. Warn him, that team-mates will see the value and can also update it after it has been unlocked. Or show a "Forbidden" message if the user does not have the permissions to change the protection.

The current implementation feels clunky and misses to communicate what its for nor how it works and how it can be undone.

Steps to Reproduce

See above

Example Repository URL

No response

Coolify Version

v4.0.0-beta.462

Are you using Coolify Cloud?

Yes (Coolify Cloud)

Operating System and Version (self-hosted)

No response

Additional Information

No response