Resource Explorer
Visual resource browser for developers and system maintainers, with manifest editing.
Overview
Most of the work of running a Hantera_ instance is answering questions about it. Which rules listen to this event? What does this job actually do? Which app contributed that graph node? Who holds this role? Each of those questions has an answer somewhere, and finding it usually means knowing where to look first.
Resource Explorer puts them all in one tree. Apps, components, rules, jobs, egresses, ingresses, graph nodes, registry entries and IAM resources are browsable side by side, and opening any of them shows the manifest behind it. Where a resource is editable, it can be changed and applied from the same place — resources that an app manages are marked read-only, so generated definitions are not quietly edited by hand.
It is aimed at the people who build and maintain the platform rather than the people working orders through it: developers, implementation partners and whoever ends up answering “why is it configured like that?”
What it does
-
One tree for every resource
Browse apps, components, rules, jobs, egresses, ingresses, graph nodes, registry entries, IAM principals, clients and roles from a single navigable tree.
-
Inspect any resource
Open a resource to see its manifest and current state, without assembling the picture from several different portal views.
-
Edit manifests in place
Change a resource's manifest from the editor and apply it, with app-managed resources marked read-only so generated definitions are not edited by hand.
-
Look up live data
Query graph nodes and open individual instances, so a definition can be checked against the data actually sitting behind it.
-
Part of the portal
Adds itself to the portal's system section, so it is available to anyone with the right permissions without a separate tool or login.