✨ Expose technical api #44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brasseld
requested changes
Jan 20, 2020
mickaelalibert
force-pushed
the
expose-technical-api
branch
3 times, most recently
from
a61fdad
to
cfe9aa0
Compare
|
LGTM. Please squash your 4 commits into a single one. |
mickaelalibert
force-pushed
the
expose-technical-api
branch
from
cfe9aa0
to
ed81080
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
Improvement in configurability
What this PR does / why we need it:
This PR allows to expose the technical api of the management app for monitoring purposes
Which issue(s) this PR fixes:
None