Closed tthvo closed 5 months ago
Probably related to/same as https://github.com/cryostatio/cryostat3/issues/406
Oh actually, I am seeing that the front-end expects the custom target to have nodeType
to be CustomTarget
according to its allowList:
Currently, for cryostat3, the custom target has nodeType JVM
. Should it be CustomTarget
instead like previously?
Ah, I see.
I think that's an OK fix in the short term, but longer term I would rather it use the JVM nodeType and have the front-end determine which nodes are deletable some other way. Maybe by checking the REALM annotation?
I think that's an OK fix in the short term, but longer term I would rather it use the JVM nodeType and have the front-end determine which nodes are deletable some other way. Maybe by checking the REALM annotation?
Yeah, check for REALM annotation sounds good to me! I can help see if there can be a quick change on the front-end...
Current Behavior
There are no delete button for custom targets.
Expected Behavior
Custom Target should be deletable from topology view through quick action menu.
Steps To Reproduce
main
commit, runbash smoketest.bash
.localhost:9091
.Environment
Anything else?
The same behaviour when deploying on k8s.