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
Add a /properties endpoint to the REST API #1420
Comments
p013570
added
enhancement
Improvement to existing functionality/feature
p:normal
labels
Oct 13, 2017
This was referenced Oct 13, 2017
t616178
added a commit
that referenced
this issue
Oct 27, 2017
james010101101
added a commit
that referenced
this issue
Oct 27, 2017
…ttps://github.com/gchq/Gaffer into gh-1420-Add-a-/properties-endpoint-to-the-REST-API
p013570
added a commit
that referenced
this issue
Oct 31, 2017
p013570
added a commit
that referenced
this issue
Oct 31, 2017
p013570
added a commit
that referenced
this issue
Oct 31, 2017
…-to-the-REST-API Added a /properties endpoint, with the ability to configure which pro…
Merged into develop. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should allow a predefined set of properties/configuration to be exposed.
GET /properties should return a map of all exposed property key values.
GET /properties/{name} should return the value of the property with the given name.
The set of exposed properties should be configured in rest.properties. E.g
So /properties would return:
/properties/gaffer.properties.app-description would return:
/properties/gaffer.properties.some-hidden-property would throw some error saying something like "gaffer.properties.some-hidden-property" is not a recognised property.
The system-description property could then be used in issue #1419.
The text was updated successfully, but these errors were encountered: