Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore: Avoid unneeded permission updates when EE license is applied #26253

Merged
merged 1 commit into from
Jul 13, 2022

Conversation

sampaiodiego
Copy link
Member

Proposed changes (including videos or screenshots)

This was happening on startup for EE or whenever a new license was applied, causing all permissions to be updated without changing anything. The fix was to add to the query the value being pulled, so only affected permissions will be updated, which should be none most of the times.

Issue(s)

Steps to test or reproduce

Further comments

@sampaiodiego sampaiodiego requested a review from a team July 13, 2022 15:44
@ggazzo ggazzo added stat: ready to merge PR tested and approved waiting for merge and removed stat: needs QA labels Jul 13, 2022
@sampaiodiego sampaiodiego added this to the 4.8.2 milestone Jul 13, 2022
@ggazzo ggazzo changed the title Chore: Fix unneeded permission updates when EE license is applied Chore: Avoi unneeded permission updates when EE license is applied Jul 13, 2022
@ggazzo ggazzo changed the title Chore: Avoi unneeded permission updates when EE license is applied Chore: Avoid unneeded permission updates when EE license is applied Jul 13, 2022
@sampaiodiego sampaiodiego merged commit c49aff1 into develop Jul 13, 2022
@sampaiodiego sampaiodiego deleted the fix-mass-permission-update branch July 13, 2022 18:03
@sampaiodiego sampaiodiego mentioned this pull request Jul 20, 2022
@murtaza98 murtaza98 mentioned this pull request Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat: QA skipped stat: ready to merge PR tested and approved waiting for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants