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
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.
The text was updated successfully, but these errors were encountered:
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.
The SKUPPER_HOME path is determined at runtime based on:
Basically if you are root, your Skupper home should be:
/usr/local/share/skupper/namespaces/
If you are not root, then:
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 theskupper home, even if there is no site yet defined.
The text was updated successfully, but these errors were encountered: