Skip to content

Conversation

@rabbah
Copy link
Member

@rabbah rabbah commented Apr 25, 2019

The setting of a namespace in wskprops can lead to surprising failures when it does not match the auth key. This value used to be there when namespaces and keys were not 1-1 but that hasn't been the case for a long time.

This patch remove --namespace from property set/unset but preserves --namespace in property get.

Partially fixes #137. Will open a subsequent PR to re-purpose wsk namespace get.

@neerajmangal
Copy link
Contributor

sorry @rabbah, for the late response. I tested the changes and all looks good.

@sciabarracom
Copy link

I built the cli and I tried with an existing configuration with a namespace:

Old:
wsk -i action list
error: Unable to obtain the list of actions for namespace 'neuronix_cloud': The supplied authentication is not authorized to access 'neuronix_cloud'. (code nVQD2dAZZbjgN4Z1fqsXkE7Q8aAFVFSi)
Run 'wsk --help' for usage.

New:
./wsk -i action list
actions

Copy link

@sciabarracom sciabarracom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works for me

@rabbah rabbah merged commit 2d2d673 into apache:master May 7, 2019
@rabbah
Copy link
Member Author

rabbah commented May 7, 2019

Thanks @neerajmangal @sciabarracom.

@devaughnsaxa
Copy link

@rabbah I think this doc needs update then
https://openwhisk.apache.org/documentation.html#wsk-cli

It still shows the --namespace flag

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 this pull request may close these issues.

remove NAMESPACE from wskprops file and wsk property subcommand

4 participants