NABSL -o yaml does not work

[Joeavaikath]

Despite registering nonadmin scheme, this does not work with output

[weshayutin]

 oc oadp nonadmin bsl get nacuser1 -o yaml


apiVersion: oadp.openshift.io/v1alpha1
kind: NonAdminBackupStorageLocation
metadata:
  creationTimestamp: "2026-02-17T19:15:15Z"
  finalizers:
  - nonadminbackupstoragelocation.oadp.openshift.io/finalizer
  generation: 1
  managedFields:
  - apiVersion: oadp.openshift.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:backupStorageLocationSpec:
          .: {}
          f:config:
            .: {}
            f:region: {}
          f:credential: {}
          f:objectStorage:
            .: {}
            f:bucket: {}
            f:prefix: {}
          f:provider: {}
    manager: kubectl-create
    operation: Update
    time: "2026-02-17T19:15:15Z"
  - apiVersion: oadp.openshift.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"nonadminbackupstoragelocation.oadp.openshift.io/finalizer": {}
    manager: manager
    operation: Update
    time: "2026-02-17T19:15:15Z"
  - apiVersion: oadp.openshift.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:conditions: {}
        f:phase: {}
        f:veleroBackupStorageLocation:
          .: {}
          f:nacuuid: {}
          f:name: {}
          f:namespace: {}
          f:status:
            .: {}
            f:lastSyncedTime: {}
            f:lastValidationTime: {}
            f:phase: {}
    manager: manager
    operation: Update
    subresource: status
    time: "2026-02-17T20:56:45Z"
  name: nacuser1
  namespace: nacuser1
  resourceVersion: "3056203"
  uid: ecf3021c-e5ba-4bab-9930-1dc96e45b4dd
spec:
  backupStorageLocationSpec:
    config:
      region: us-west-2
    credential:
      key: cloud
      name: cloud-credentials
    objectStorage:
      bucket: wesoadpnacuser1
      prefix: velero
    provider: aws
status:
  conditions:
  - lastTransitionTime: "2026-02-17T19:15:15Z"
    message: NonAdminBackupStorageLocation spec validation successful
    reason: BslSpecValidation
    status: "True"
    type: Accepted
  - lastTransitionTime: "2026-02-17T19:15:44Z"
    message: NonAdminBackupStorageLocationRequest approval decision set to Approve
    reason: BslSpecApproved
    status: "True"
    type: ClusterAdminApproved
  - lastTransitionTime: "2026-02-17T19:15:44Z"
    message: Secret successfully created in the OADP namespace
    reason: SecretCreated
    status: "True"
    type: SecretSynced
  - lastTransitionTime: "2026-02-17T19:15:44Z"
    message: BackupStorageLocation successfully created in the OADP namespace
    reason: BackupStorageLocationCreated
    status: "True"
    type: BackupStorageLocationSynced
  phase: Created
  veleroBackupStorageLocation:
    nacuuid: nacuser1-nacuser1-206fbc4c-dfe4-4c97-8f4c-3b8a75ffb674
    name: nacuser1-nacuser1-206fbc4c-dfe4-4c97-8f4c-3b8a75ffb674
    namespace: openshift-adp
    status:
      lastSyncedTime: "2026-02-17T20:56:25Z"
      lastValidationTime: "2026-02-17T20:56:45Z"
      phase: Available

nacuser1@fedora:~/git/oadp-cli$ 

[Joeavaikath]

oc oadp na create bsl test01 --provider=aws --bucket=jvaikath-velero --prefix=velero --credential cloud-credentials=cloud --region us-east-1 -o yaml 
An error occurred: no kind is registered for the type v1alpha1.NonAdminBackupStorageLocation in scheme "pkg/runtime/scheme.go:110"

happens when you try with create; scheme issue in create.go specifically

[weshayutin]

@Joeavaikath wth heck is a create w/ -o yaml ????? When does that ever work?
I've never seen anyone run an oc create w/ -o yaml .. maybe I'm not understanding something

[Joeavaikath]

it's used to get the yaml like it's a dry run
doesn't do the create, just outputs the yaml

[weshayutin]

@Joeavaikath ok.. just tried this.. w/ dpa creation.

 oc create -f dpa.yaml -o yaml
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  creationTimestamp: "2026-02-18T14:28:35Z"
  generation: 1
  name: dpa-sample
  namespace: openshift-adp
  resourceVersion: "3340891"
  uid: 940a7e46-ac03-4621-b291-1011123259a8
spec:
  backupLocations:
  - velero:
      config:
        profile: default
        region: us-east-1
      credential:
        key: cloud
        name: cloud-credentials
      default: true
      objectStorage:
        bucket: velero-6109f5e9711c8c58131acdd2f490f452
        prefix: westestvelero
      provider: aws
  configuration:
    nodeAgent:
      enable: true
      loadConcurrency:
        globalConfig: 3
      uploaderType: kopia
    velero:
      concurrentBackups: 3
      defaultPlugins:
      - kubevirt
      - csi
      - openshift
      - aws
      - hypershift
      disableFsBackup: false
      logLevel: debug
  logFormat: text
  vmFileRestore:
    enable: false

imho this is a low priority issue, but apparently valid. It's also NOT a dry-run