Skip to content

Provide hateoas discoverabilty of actuator endpoints without spring-hateoas #6887

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.

Sign up for GitHub

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

Jump to bottom
Closed
philwebb opened this issue Sep 14, 2016 · 5 comments
Closed

Provide hateoas discoverabilty of actuator endpoints without spring-hateoas #6887

philwebb opened this issue Sep 14, 2016 · 5 comments
Labels
status: duplicate A duplicate of another issue type: enhancement A general enhancement

Comments

@philwebb
Copy link
Member

It would be nice if the current /actuator endpoint worked even if spring-hateoas isn't in use. Particularly if systems are in place that want to know what endpoints are available without hitting each one individually.
@philwebb philwebb added the type: enhancement A general enhancement label Sep 14, 2016
@philwebb philwebb added this to the 1.5.0 M1 milestone Sep 14, 2016
@philwebb
Copy link
Member Author

Related to #6886 which would be the obvious place to put this endpoint.

@mbhave mbhave self-assigned this Oct 14, 2016
@mbhave
Copy link
Contributor

mbhave commented Dec 6, 2016

Done as part of #7108. The CloudFoundryDiscoveryEndpoint returns a HAL response for the Cloud Foundry actuators even when spring-hateoas is not in use.

@mbhave mbhave closed this as completed Dec 6, 2016
@philwebb philwebb reopened this Dec 7, 2016
@philwebb
Copy link
Member Author

philwebb commented Dec 7, 2016

I think we only did this for the CloudFoundryDiscoveryEndpoint, we should consider if we want it also for the regular actuators endpoint.

@mbhave
Copy link
Contributor

mbhave commented Dec 7, 2016

Good point. I suppose we can add support for this in the HalJsonMvcEndpoint. The HalBrowserMvcEndpoint, I think, would still require spring-hateoas.

@mbhave mbhave added the for: team-attention An issue we'd like other members of the team to review label Dec 8, 2016
@mbhave mbhave modified the milestones: 2.0.0.M1, 1.5.0 M1 Dec 8, 2016
@mbhave mbhave removed the for: team-attention An issue we'd like other members of the team to review label Dec 16, 2016
@philwebb philwebb modified the milestones: 2.0.0.M1, 2.0.0 Jan 12, 2017
@mbhave mbhave removed their assignment Jan 18, 2017
@wilkinsona
Copy link
Member

Duplicate of #9901

@wilkinsona wilkinsona marked this as a duplicate of #9901 Jul 29, 2017
@wilkinsona wilkinsona added the status: duplicate A duplicate of another issue label Jul 29, 2017
@wilkinsona wilkinsona removed this from the 2.0.0 milestone Jul 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: duplicate A duplicate of another issue type: enhancement A general enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@philwebb @wilkinsona @mbhave