Delete all nonkube resources for a given namespace

[fgiorgetti]

We need a way to delete the whole namespace directory.
For example. Consider that a user created multiple resources, using the CLI, like:

skupper -n west site create
skupper -n west listener create backend 8080

Then the user simply wants to delete the whole ~/.local/share/skupper/namespaces/west directory.
This is something that could be added to skupper system delete (or even to skupper system stop) as a flag.

[nluaces]

@fgiorgetti in this pull request skupperproject/skupper#2003, system stop is removing the whole namespace directory, you can choose the directory to delete with the flag -n, if not it will delete the default namespace/directory.

[fgiorgetti]

The only problem with the system stop is that it is only executed when there is a running site on the given namespace.

Looking at refdog earlier today, I noticed that we already have the site delete --all, but it does not remove the namespace directory itself (i.e.: .local/share/skupper/namespaces/default).

Do you all think that it would be appropriate to remove the namespace directory when running site delete --all ?

[lynnemorrison]

@fgiorgetti I do think that site delete --all should also delete the namespace directory
In Kube we delete all the resources in the specified namespace, listeners, connectors, accessgrants, routeraccesses, ...

As @nluaces says in the system uninstall --force we also delete the namespace directory

[fgiorgetti]

@lynnemorrison I think that the site delete --all should only remove the whole directory if the namespace
is NOT active or running. Otherwise, removing it would leave containers, systemd services and processes behind.

If the namespace is "active", then just remove the input files.

Thoughts?

[lynnemorrison]

@fgiorgetti agree, I'll update the site delete -all to remove the whole directory if namespace is not active.
If the namespace is "active", then just remove the input files.

Should we add a log that indicates the site is active so user should use "skupper system uninstall --force" to remove the active sites
or skupper system stop -n

[fgiorgetti]

I believe recommending system stop makes sense if the namespace is active.

[lynnemorrison]

currently "skupper site delete" doesn't check for an active site.
if --all flag is not set it deletes the namespace//input/resources/site-"name".yaml and the router-access-"name".yaml files
if --all flag is set it remotes entire directory and all files in namespace/

new code will do:
if --all is not set stay the same as above (so even if site is active it will just delete the above two files)
if --all flag is set code will check for an active site in namespace//runtime/resources/ and if found provide a message to user to "site XXX is still active. Use "skupper system stop -n " to remove an active site