Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic creation of $HOME/.itools ? #2482

Closed
geofjamg opened this issue Mar 2, 2023 · 0 comments · Fixed by #2492
Closed

Automatic creation of $HOME/.itools ? #2482

geofjamg opened this issue Mar 2, 2023 · 0 comments · Fixed by #2492
Assignees

Comments

@geofjamg
Copy link
Member

geofjamg commented Mar 2, 2023

  • 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)

@geofjamg geofjamg changed the title Automatic creation of $HOME/.itools Automatic creation of $HOME/.itools ? Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants