Checklist
Enhancement purpose
ASF supports work with no specified password (or other sensitive data), that can be requested by on-demand basis via console or input command. But if password is already set in config - ASF-ui have no means to remove it, only to replace it with another one, if field is left empty - old value preserved.
Solution
I suggest to add a checkbox or a button to allow users to specify that ASF-ui should actually send null instead of password to remove it from config file. Similar logic can be applied to other sensitive fields, at least the ones that allow requesting them via console/input command.
Why currently available solutions are not sufficient?
If ASF-ui supports editing config files - removing properties should be available too.
Can you help us with this enhancement idea?
Somehow, I can test and offer feedback, but can't code
Additional info
Honestly, I don't even need it personally. But since I noticed lack of this possibility I decided to report it, and the rest is up to you.
Checklist
Enhancement purpose
ASF supports work with no specified password (or other sensitive data), that can be requested by on-demand basis via console or input command. But if password is already set in config - ASF-ui have no means to remove it, only to replace it with another one, if field is left empty - old value preserved.
Solution
I suggest to add a checkbox or a button to allow users to specify that ASF-ui should actually send
nullinstead of password to remove it from config file. Similar logic can be applied to other sensitive fields, at least the ones that allow requesting them via console/inputcommand.Why currently available solutions are not sufficient?
If ASF-ui supports editing config files - removing properties should be available too.
Can you help us with this enhancement idea?
Somehow, I can test and offer feedback, but can't code
Additional info
Honestly, I don't even need it personally. But since I noticed lack of this possibility I decided to report it, and the rest is up to you.