Update github.com/opiproject/opi-api digest to ca2c25b

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/opiproject/opi-api	require	digest	ffe4aad -> ca2c25b

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #20 (6f18655) into main (eb15131) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff          @@
##            main     #20   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          3       3           
  Lines        547     579   +32     
=====================================
- Misses       547     579   +32     

Impacted Files	Coverage Δ
frontend.go	0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[benlwalker]

Technically, a user could do this sequence of steps:

1. Create subsystem
2. Create namespace
3. Create controller

In this case, it needs to go add all the namespaces to the controller inside the CreateNvmeController call.

[glimchb]

This is why I thought we should keep the API calls separate and mandate CTRL-id when you create NS and if not provided, it does the for-loop...

[benlwalker]

A namespace can't be in just a single controller, so the namespace having a controller id isn't sufficient. Image this scenario:

1. Create subsystem.
2. Create controller.
3. Create namespace (with controller id)
4. Create a second controller

Where some time passes between step 3 and 4. That's a valid thing to do and it needs to be handled. Now the namespace should be in two controllers. That's the reason I removed controller_id from the namespace object - it doesn't model the relationship correctly.

[glimchb]

I would imagine :
5. Create a namespace (with second controller id)

[benlwalker]

So now you have two namespace resources representing the same physical object?