NABSL requests not seen when not in the same namspace

[Joeavaikath]

have to switch the project in which  the NABSL is created, then only i am able to see. Which should not be the case. Admin should be able to see requests from all non-admin namespaces from openshift-adp.. (edited)

[weshayutin]

@Joeavaikath hrm.. not sure if I understand this one.. ping me when you have time

[weshayutin]

ok.. I think I get this now..
IMHO..

Looking at the doc we have things broken into distinct perspectives.

Cluster Admin: https://docs.okd.io/latest/backup_and_restore/application_backup_and_restore/oadp-self-service/oadp-self-service-cluster-admin-use-cases.html

Namespace Admin / non-admin user: https://docs.okd.io/latest/backup_and_restore/application_backup_and_restore/oadp-self-service/oadp-self-service-namespace-admin-use-cases.html

IMHO: The admin use case

• setting up the DPA
• approving / rejecting nabsl requests

These actions are NOT appropriate for the cli and should NOT be made available.
@mpryc @shubham-pampattiwar wdyt?

IMHO the oadp-cli oc oadp nonadmin should be scoped only to namespace admin ( non-admin ) chores/tasks.

[shubham-pampattiwar]

Looking at the code, the --all-namespaces flag exists on nabsl-request get but doesn't appear to be wired up - the Run() function always uses the current namespace.

Admin tasks like approve/reject are already under oc oadp nabsl-request, separate from oc oadp nonadmin, so the separation already exists.

[Joeavaikath]

The --all-namespaces is actually a misnomer: the requests are created on the admin namespace (where the velero server exists)
Right now it's incorrectly wired to use current namespace like it's a nonadmin command, will be fixed in #138

• Scope: Namespace-scoped (same namespace as the OADP operator)