Added Tenant support #13
Merged
Conversation
This file contains hidden or 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
Owner
|
Looks good. I'll merge and release it tonight |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
With tenants we should be able to deploy multiple instances of our project into the same environment.
Also it gives one more scope for variables and stuff.
In order to achieve this we need to add Tenants and TagSets support as these are two closely related entities.
Tenants has links to projects and envs, projects themself (from config perspective) are not aware of tenants, also db structure approving this.
Scoping is made through TagSets (Tenants is like container for TagSet). And project has one more property to make it tenant friendly.
Also tentacles should be updated with tenants/tags in order to make tenanted deploy but this is out of this projects scope :)