[Bug] Subviews like `/recordings/create` are not accessible when visited directly

[tthvo]

Current Behavior

If I directly visit views by specifying their paths such as:

/topology/create-custom-target
/rules/create
/recordings/create

For example, https://cryostat-sample-myns.apps-crc.testing/recordings/create. A blank page is showed:

with the following console's error:

Expected Behavior

The sub views should render correctly!

Steps To Reproduce

• Launch an OpenShift instance. For example, with OpenShift Local, crc start.
• On latest cryostat-operator's commit on main:

  make deploy_bundle create_cryostat_cr sample_app

Environment

CRC version: 2.26.0+233df0
OpenShift version: 4.13.9
OS: Fedora 40

Anything else?

This only happens if I visit the sub-view directly. That is: If I go /recordings -> Click Create -> /recordings/create, all is fine.

[andrewazores]

Seems like going to /recordings/create makes the client try to look for the other asset bundles relative to /recordings instead of relative to /, so it tries to load /recordings/runtime.abcd1234.bundle.js instead of /runtime.abcd1234.bundle.js. Cryostat doesn't recognize this path so it responds with the index.html again, which results in the MIME type and SyntaxError errors.

Probably happening since #1175 then.

[andrewazores]

Now that the standard Cryostat deployment includes an auth proxy, it might be possible to solve the original https://github.com/cryostatio/cryostat/issues/1810 using an auth proxy configuration plus Route/Ingress path configuration, and back out #1175.

[andrewazores]

This affects 2.4.1-snapshot too so I'm pretty sure #1175 is the culprit.

[tthvo]

Seems like going to /recordings/create makes the client try to look for the other asset bundles relative to /recordings instead of relative to /, so it tries to load /recordings/runtime.abcd1234.bundle.js instead of /runtime.abcd1234.bundle.js. Cryostat doesn't recognize this path so it responds with the index.html again, which results in the MIME type and SyntaxError errors.
This affects 2.4.1-snapshot too so I'm pretty sure #1175 is the culprit.

Right, make sense! That explained the logged error :(

Now that the standard Cryostat deployment includes an auth proxy, it might be possible to solve the original https://github.com/cryostatio/cryostat/issues/1810 using an auth proxy configuration plus Route/Ingress path configuration, and back out #1175.

Just curious what's the plan for this fix?

[andrewazores]

Currently no plan, that was just a very rough idea. It would be nice to have the ability to go directly to paths like /recordings/create, but not if it comes at the expense of becoming impossible to deploy Cryostat instances on paths other than /.

[tthvo]

I am thinking if no errors with with the regular single level /recordings, we can make /recordings/create route into /create-recording for the sub view, basically flattening the route paths. That should help with the issue? Might not be the best UX.

[andrewazores]

That's one potential way around, but I think it's pretty limiting. It makes sense right now because none of the UI paths are parameterized, so applying such a transformation looks like it works. It wouldn't work anymore if we had any paths like /topology/:nodeId (just a random example), and adopting such a scheme would block us from ever having paths like that in the future.