This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Fixed Contacts behavior#109
Merged
rvelaVenafi merged 1 commit intomasterfrom Apr 26, 2022
Merged
Conversation
Fixed the behavior of the policy specification users list when updating a VaaS policy: 1. If there are no contacts in the PS and the application does not exist in VaaS, the application will be created with the current user as the only owner of the application. 2. If there are no contacts in the PS and the application exists, the owners of the application should not be changed. 3. If there are contacts in the PS, the owners of the application should exactly match the PS (regardless of whether the application is being created or already exists).
ricrodriguezg
approved these changes
Apr 26, 2022
marcos-albornoz
approved these changes
Apr 26, 2022
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixed the behavior of the policy specification users list when updating a VaaS policy: