Add qualified name to make suborganizations' names unique per parent #1846
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
sleshchenko
force-pushed
the
compositeNamespace
branch
5 times, most recently
from
a8ef16a
to
361ab8f
Compare
slemeur
approved these changes
Feb 28, 2017
sleshchenko
force-pushed
the
compositeNamespace
branch
from
361ab8f
to
eb93612
Compare
|
Fixing of reviewers' comments and adding migration scripts(for setting qualified names for existing suborganizations) will be done in another PR. |
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 does this PR do?
Add qualified name to make suborganizations' names unique per parent organization
What issues does this PR fix or reference?
#1674
Changelog
Release Notes
N/A part of teams
Docs PR
N/A part of teams