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
This issue is to track the gaps in NSFS documentation and CLI help command.
notification is missing CLI help command
Please run: sudo node src/cmd/manage_nsfs --help 2>/dev/null
And see:
<type> Set the resource type: account, bucket, whitelist, diagnose, logging or upgrade
(notifications also need to appear here).
noobaa-cli upgrade <> CLI command do have CLI_MUTUAL_FLAGS? If yes we need to update it in upgrade help doc.
If logging and diagnose commands are permitted when upgrading noobaa, then we need to update it under UPGRADE_START_OPTIONS.
Check if we need to expand the text in: upgrade start
Please run: sudo node src/cmd/manage_nsfs upgrade start --help 2>/dev/null
And see:
and NooBaa CLI Account/Buckets/Whitelist getters operations will still be working
But updates of the config directory will be blocked during the upgrade of the config directory.
Do we want to refer also to other noobaa-cli commands here? (logging, notifications, diagnose, etc.)
Update documentation on: logging, notifications
The text was updated successfully, but these errors were encountered:
Environment info
Actual behavior
This issue is to track the gaps in NSFS documentation and CLI help command.
Please run:
sudo node src/cmd/manage_nsfs --help 2>/dev/null
And see:
(notifications also need to appear here).
noobaa-cli upgrade <>
CLI command do have CLI_MUTUAL_FLAGS? If yes we need to update it in upgrade help doc.If logging and diagnose commands are permitted when upgrading noobaa, then we need to update it under
UPGRADE_START_OPTIONS
.Check if we need to expand the text in:
upgrade start
Please run:
sudo node src/cmd/manage_nsfs upgrade start --help 2>/dev/null
And see:
Do we want to refer also to other noobaa-cli commands here? (logging, notifications, diagnose, etc.)
The text was updated successfully, but these errors were encountered: