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
Do you want to request a feature or report a bug?
Design issue
What is the current behavior?
When using the classic config provider, at creation of the PlatformConfigsingleton, we automatically create this directory if not exists. Even if we don't use any config.yml file inside. We already add 2 external bad feedbacks on this, because it could be in some system an issue to require a write access to file system when only using PowSyBl functions that are not supposed to write anything (like loading a file, running a LF).
What is the expected behavior?
We could let the user, creating the directory and consider that if not exist, there is just not config.yml file (obviously!).
What is the motivation / use case for changing the behavior?
Not requiring file system write access, when it is not needed.
Please tell us about your environment:
PowSyBl Version: ...
OS Version: ...
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Design issue
What is the current behavior?
When using the classic config provider, at creation of the
PlatformConfig
singleton, we automatically create this directory if not exists. Even if we don't use any config.yml file inside. We already add 2 external bad feedbacks on this, because it could be in some system an issue to require a write access to file system when only using PowSyBl functions that are not supposed to write anything (like loading a file, running a LF).What is the expected behavior?
We could let the user, creating the directory and consider that if not exist, there is just not config.yml file (obviously!).
What is the motivation / use case for changing the behavior?
Not requiring file system write access, when it is not needed.
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered: