ACNA-296 - Remove `namespace` from .wskprops

[shazron]

Motivation

apache/openwhisk-cli#434

The namespace key came during a time in Openwhisk when the auth key maps to one or more namespaces. Now, there is a 1:1 mapping of auth key and namespace.

However, if we remove this key, the user can't really tell which namespace they are using at a glance, so it might serve an informational purpose still. But according to the openwhisk issue above, it can lead to surprising failures when namespace doesn't match the auth key. I think this should be a server bug however (they should ignore the namespace key).

Expected Behaviour

No namespace key and value in .wskprops

Actual Behaviour

There is a namespace key and value in .wskprops

Line

https://github.com/adobe/aio-cli-plugin-console/blob/master/src/commands/console/select-integration.js#L63

[purplecabbage]

Each project should be associated with a particular namespace and preferably stored in the project fit with the code.
I think we still need this, even if it is informational only.

[goya]

how it is now. unless theymanuallychange just the namespace the namespace isalways set during the namespace select which includes the correct auth etc..

[shazron]

ah yes, I just saw the commit in the runtime plugin. Good show

[shazron]

In the new config (with our new upcoming releases), the config for runtime is read (in order of preference):

1. CLI flag
2. runtime.xxx value
3. .wskprops

[adobe-bot]

JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-296

[shazron]

Closing this issue. We will not remove namespace in the .wskprops or runtime config, because we need a way to remember what namespace is associated with an auth key, for multiple configuration purposes.