Update README with executions endpoints and ACL example #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently I was setting up a new API token following "principle of least privilege" so that the token's user would only be able to make the minimum API calls necessary to obtain metrics from the endpoints used by
rundeck_exporter
. The official API reference isn't consistent in explaining which policies are necessary for an endpoint, so this involved a lot of trial and error. I thought it might be helpful for other users to have an example of example which policy rules are necessary forrundeck_exporter
to work.This PR:
rundeck_exporter
to include project execution endpoints, and turns each item in the bulleted list into a link to the API documentation for that endpointEditor
box.