Product created before Backend fails to sync

A Product (pr) that references a backend (pr-be)  . If the Product is created before a backend then the backend will fail to sync.

oc create -f product.yaml fails

• message: 'spec.backendUsages[pr-be]: Invalid value: v1beta1.BackendUsageSpec{Path:"/"}:
        backend usage does not have valid backend reference.'
• Conditions: Failed, Orphan

oc create -f backend.yaml - successfully created.

But product.yaml remains in the failed state and does not sync.

Requiring a backend to be created before a product is a major issue in CI/CD pipelines.

One particular use case is the Argo CD pipelines. Product and Backend can be created , deleted in the UI using a "Sync" button. A user can select both the Product and the Backend and perform a sync. The order in which backend and product is synced unspecified. And the product ends up in a non-synced failed state. The workaround would require imposing an order of backend first , followed by product either on the user (when performing Sync) introducing a delay in the pipeline (assuming it is possible) .