fix: limit microservice named lookup during create #318
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
…y the current tenant Avoid matching against microservices of the same name found in subtenant which can not be managed from the parent tenant.
…e) to only return applications owned by the current tenant
reubenmiller
force-pushed
the
fix-microservice-create-named-lookup
branch
from
d7be180 to
334ee60
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.
Avoid matching against microservices of the same name found in subtenant which can not be managed from the parent tenant.
Running
c8y microservices create --file myapp.zipwill not match match against any microservices which are not owned by the current tenant (if the tenant id is known).