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

[v2] nonkube command to show namespace specific paths #3

Open
fgiorgetti opened this issue Sep 26, 2024 · 3 comments
Open

[v2] nonkube command to show namespace specific paths #3

fgiorgetti opened this issue Sep 26, 2024 · 3 comments

Comments

@fgiorgetti
Copy link
Member

The SKUPPER_HOME path is determined at runtime based on:

  • current user (root or non-root)
  • XDG_DATA_HOME (environment variable as non-root user)

Basically if you are root, your Skupper home should be:

/usr/local/share/skupper/namespaces/

If you are not root, then:

  • XDG_DATA_HOME is set? ${XDG_DATA_HOME}/skupper/namespaces/
  • Otherwise: ${HOME}/.local/share/skupper/namespaces

As users can provide source CRs and eventually custom certificates, before initializing a nonkube site,
it would be nice if the CLI had a command or a flag that, considering the --namespace flag, shows the
skupper home, even if there is no site yet defined.

@hash-d
Copy link
Member

hash-d commented Sep 26, 2024

I find it weird to have this on /usr. Wouldn't /var/lib be a more natural place for these files?

@fgiorgetti
Copy link
Member Author

Now that users will eventually modify the content of some namespace files, maybe /var/local or/var/lib could be more appropriate. This is an implementation detail and maybe we should handle it as an issue in the Skupper repository, wdyt?

Regardless of where it will end up writing, the goal here is to have an easy way for a logged user to know where files are or will be located using the CLI.

@fgiorgetti
Copy link
Member Author

Maybe this could be presented as part of the help message of the "bootstrap" command/verb once it is incorporated into refdog.

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

No branches or pull requests

2 participants