Closed james-nesbitt closed 7 years ago
it has been on my list to write a small wrapper for the very default user-loading, to provide a default user based on OS reported user. It looks like this, and a null security wrapper are a good idea now.
to clarify: our cli is now using a secured api-builder, which applies authorization checks to all operations. The cli pulls current-user information from a config-wrapper, but does not have a fallback for "no user config exists" and is reporting "no-user" which stalls the security authorization check.
expected user yml looks like this:
-> % cat ~/.config/radi/user.yml
Id: james.nesbitt@wunder.io
Label: James Nesbitt
Default user handling now exists after https://github.com/wunderkraut/radi-cli/pull/30.
when running some radi-cli commands, we sometimes get missing operations and the following type of output:
This issue was first report https://github.com/wunderkraut/radi-project-wundertoolswrapper/issues/20