Add ability to get DSN from multiple Cloud Foundry service bindings #106
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
As a first step, the first bound Postgres instance will be used. This could be extended to support multiple bindings/postgesses.
This will prefix the service names to the metric descriptor names.
ihrigb
changed the title
|
Need to do some rework on this. |
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.
This enables the service (if
DATA_SOURCE_NAMEis not specified) to try to parseVCAP_SERVICESin order to get all bound postgres services.If it finds some, it will retrieve the URIs and enable multiple exporters. This is while
userQueriesPath-file will be applied to each of them and it will search for a file with name<cf-service-instance-name>.yml, which will be individually added.