You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reseved for future releases. Leaving it here just as an idea for now.
I like the solutionwe adopted in #217 for the TLS auth key of OpenVPN.
In many cases, configuration keys point to files.
However, the current way of defining files in this library is cumbersome for users.
Ideally users can simply paste the contents of the files, without having to define the paths.
I think the approach could be something like: if a key expects a file and the string contains any new line we can infer it's the contents of the file and we can generate the file automatically for the user.
Or something along these lines.
That way we maintain backward comaptibility.
The only issue is how to decide the path where to store the file, which we have to decide whether the user could be able to hint this in any way.
The text was updated successfully, but these errors were encountered:
Reseved for future releases. Leaving it here just as an idea for now.
I like the solutionwe adopted in #217 for the TLS auth key of OpenVPN.
In many cases, configuration keys point to files.
However, the current way of defining files in this library is cumbersome for users.
Ideally users can simply paste the contents of the files, without having to define the paths.
I think the approach could be something like: if a key expects a file and the string contains any new line we can infer it's the contents of the file and we can generate the file automatically for the user.
Or something along these lines.
That way we maintain backward comaptibility.
The only issue is how to decide the path where to store the file, which we have to decide whether the user could be able to hint this in any way.
The text was updated successfully, but these errors were encountered: