Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Feature]: Health API JSON Schema Update: Add componentType and componentCategory #479

Open
anilnatha opened this issue Sep 16, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request U-CS

Comments

@anilnatha
Copy link

anilnatha commented Sep 16, 2024

Checked for duplicates

Have you checked for duplicate issue tickets?

Yes.

Alternatives considered

Have you considered alternative solutions to your feature request?

No.

Related problems

Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets.

The UI/UX team had originally designed the UI's navbar to have categories to help organize links in the navbar and make it easier for users to find what they are looking for.

In addition, we expect the health API to include services (e.g. APIs, etc.) that a user wouldn't typically navigate to in a browser. So, we would need to know which of those items returned by the health API endpoint are items that have a UI the user should access.

Here is an example screenshot of the originally proposed navbar design:

image

Describe the feature request

The UI/UX team would like to propose the addition of two new fields that when filled in, helps bucket components into meaningful categories in the UI's navbar and help inform us of what should be added to the navbar as a navigable item. The values set in this field should be restricted to a specific set of values and those listed below are to get the conversation started on what the values should be.

FIeld Name Possible Values
componentCategory administration, catalogs, development, infrastructure, processing
componentType api, ui, service

Example:

{
	"componentName": "Management Console",
        "componentCategory": "administration",
        "componentType": "ui",
	"ssmKey": "/unity/ramesh/hc1/component/management-console",
	...
},
{
	"componentName": "Health API",
        "componentCategory": "infrastructure",
        "componentType": "api",
	"ssmKey": "/unity/ramesh/hc1/component/management-console",
	...
}

@rtapella Please chime in on what I have posted above to ensure the accuracy of the request and fill in any missing details, and if we want to add/change the list of possible values for each of the fields.

@anilnatha anilnatha added the enhancement New feature or request label Sep 16, 2024
@anilnatha
Copy link
Author

anilnatha commented Sep 16, 2024

A comment regarding

And we also would like to be able to know which items returned by the endpoint should be added to the navbar so that the health endpoint isn't restricted to only reporting on services that a user can navigate to in a browser.

Only those components that have their componentType set to ui would be added to the navbar. In addition, on the health dashboard, we could potentially add these two fields listing the components category and type.

@anilnatha
Copy link
Author

@galenatjpl Any updates regarding this feature request and if it can be completed in 24.4?

@galenatjpl galenatjpl self-assigned this Nov 15, 2024
@galenatjpl
Copy link
Collaborator

@anilnatha I'm not yet sure if we can complete this in 24.4, but I think it's probable. I just think there are some other larger higher priority tickets still in the kitchen currently

@rtapella
Copy link

agreed.
also Description would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request U-CS
Projects
None yet
Development

No branches or pull requests

3 participants