Uh oh!
There was an error while loading. Please reload this page.
Select single permissions level per principal - #3904
Merged
Conversation
Collaborator
14 failing tests:
Top 33 slowest tests (at least 2 minutes):
|
denik
marked this pull request as ready for review
November 11, 2025 14:25
denik
requested review from
andrewnester, anton-107, pietern and shreyas-goenka
as code ownersNovember 11, 2025 14:25
denikforce-pushed
the
denik/permissions-testserver
branch
from
November 11, 2025 15:12
d4db81f to
4409c34Comparepietern
reviewed
Nov 11, 2025
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
denikforce-pushed
the
denik/permissions-testserver
branch
from
November 12, 2025 11:57
b23087e to
aec1336Comparedenikforce-pushed
the
denik/permissions-testserver
branch
from
November 12, 2025 12:17
aec1336 to
8d976c9Comparedenikforce-pushed
the
denik/permissions-testserver
branch
from
November 12, 2025 14:43
735bcf4 to
90356daComparedenik
enabled auto-merge
November 12, 2025 14:56
andrewnester
approved these changes
Nov 12, 2025
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
denik added a commit
that referenced
this pull request
Nov 13, 2025
denik added a commit
that referenced
this pull request
Nov 13, 2025
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Nov 13, 2025
## Release v0.277.0 ### Bundles * Add `default-minimal` template for users who want a clean slate without sample code ([#3885](#3885)) * Add validation that served_models and served_entities are not used at the same time. Add client side translation logic. ([#3880](#3880)) * Filter out provided permissions, to select a single permissions level per principal (([#3904](#3904))).
denik added a commit
that referenced
this pull request
May 20, 2026
## Changes When multiple permissions are present, select one per principal (highest of all available), ## Why Backend only stores one permission level per principal, whatever is latest in the request. So if users define multiple levels for the same principal, arbitrary level is going to be send to the backend, just whatever happens to be last in request. In some case, terraform will reject multiple levels and error. Why we select max level: The intent is usually to have some default permissions applied broadly (e.g., CAN_VIEW) and then grant higher permission (e.g. CAN_MANAGE) to selected principal, in which case principal has both CAN_VIEW and CAN_MANAGE which is the same as just CAN_MANAGE. Should fix#3864 ## Tests New acceptance test. Fix testserver to match real backend as tested by #3900
denik added a commit
that referenced
this pull request
May 20, 2026
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.277.0 ### Bundles * Add `default-minimal` template for users who want a clean slate without sample code ([#3885](#3885)) * Add validation that served_models and served_entities are not used at the same time. Add client side translation logic. ([#3880](#3880)) * Filter out provided permissions, to select a single permissions level per principal (([#3904](#3904))).
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 freeto 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.
Changes
When multiple permissions are present, select one per principal (highest of all available),
Why
Backend only stores one permission level per principal, whatever is latest in the request. So if users define multiple levels for the same principal, arbitrary level is going to be send to the backend, just whatever happens to be last in request. In some case, terraform will reject multiple levels and error.
Why we select max level: The intent is usually to have some default permissions applied broadly (e.g., CAN_VIEW) and then grant higher permission (e.g. CAN_MANAGE) to selected principal, in which case principal has both CAN_VIEW and CAN_MANAGE which is the same as just CAN_MANAGE.
Should fix#3864
Tests
New acceptance test.
Fix testserver to match real backend as tested by #3900