dynamic database name #807
Open
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
Feature: database name can be dynamicaly provided as string oder context variable on "mongo in" and "mongo out"
|
Do you have a link to where this change was discussed (Slack or Forum)? |
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.
Feature: database name can be dynamicaly provided as string oder context variable on "mongo in" and "mongo out"
Proposed changes
missing feature to provide database name optionaly as context variable for example to use req.headers.host (without port) as database name. With that you can use same application with diferent data backends definded by query parameter, post data or in my case with domain name.
Checklist
gruntto verify the unit tests pass