If someone tries to run: nb account create --allow_bucket_create false -n test1 (without the account name) it creates an account with the name false.
Flags names contain underscore instead of hyphen, for example: --allow_bucket_create.
When using the nb account delete get the error: FATA[0000] ❌ Missing expected arguments: <bucket-class-name> which doesn't have the same argument as the usage: noobaa account delete <noobaa-account-name> [flags] [options].
Expected behavior
It should throw an error Missing expected arguments: <noobaa-account-name>.
Flags names should contain hyphens between words, for example: --allow_bucket_create
It should throw error FATA[0000] ❌ Missing expected arguments: <noobaa-account-name> on nb account delete.
Steps to reproduce
Deploy noobaa system on k8s cluster (can use local deployment).
Every number is for one issue:
nb account create --allow_bucket_create false -n test1
nb account create --help
noobaa account delete
More information - Screenshots / Logs / Other output
Output: nb account create --allow_bucket_create false -n test1
INFO[0000] ✅ Exists: NooBaa "noobaa"
INFO[0000] ✅ Created: NooBaaAccount "false"
INFO[0000]
INFO[0000] NOTE:
INFO[0000] - This command has finished applying changes to the cluster.
INFO[0000] - From now on, it only loops and reads the status, to monitor the operator work.
INFO[0000] - You may Ctrl-C at any time to stop the loop and watch it manually.
INFO[0000]
INFO[0000] NooBaaAccount Wait Ready:
INFO[0000] ⏳ NooBaaAccount "false" Phase is "": waiting...
INFO[0003] ✅ NooBaaAccount "false" Phase is Ready
INFO[0003]
INFO[0003]
INFO[0003] ✅ Exists: NooBaaAccount "false"
INFO[0003] ✅ NooBaaAccount "false" Phase is Ready
# NooBaaAccount spec:
allow_bucket_creation: true
default_resource: noobaa-default-backing-store
force_md5_etag: false
INFO[0003] ✅ Exists: Secret "noobaa-account-false"
Connection info:
AWS_SECRET_ACCESS_KEY : ****
AWS_ACCESS_KEY_ID : ****
Environment info
NooBaa Operator Version: Current master (5.17.0) Platform: Kubernetes v1.27.3 | Rancher Desktop 1.12.3
Actual behavior
nb account create --allow_bucket_create false -n test1
(without the account name) it creates an account with the name false.--allow_bucket_create
.nb account delete
get the error:FATA[0000] ❌ Missing expected arguments: <bucket-class-name>
which doesn't have the same argument as the usage:noobaa account delete <noobaa-account-name> [flags] [options]
.Expected behavior
Missing expected arguments: <noobaa-account-name>
.--allow_bucket_create
FATA[0000] ❌ Missing expected arguments: <noobaa-account-name>
onnb account delete
.Steps to reproduce
Deploy noobaa system on k8s cluster (can use local deployment). Every number is for one issue:
nb account create --allow_bucket_create false -n test1
nb account create --help
noobaa account delete
More information - Screenshots / Logs / Other output
Output:
nb account create --allow_bucket_create false -n test1