Skip to content

Comments

feat: Include system assignments in the list_for_multiple_actors_and_targets method#426

Merged
gtema merged 1 commit intoopenstack-experimental:mainfrom
konac-hamza:fix/system-assignments-issue-143-clean
Dec 8, 2025
Merged

feat: Include system assignments in the list_for_multiple_actors_and_targets method#426
gtema merged 1 commit intoopenstack-experimental:mainfrom
konac-hamza:fix/system-assignments-issue-143-clean

Conversation

@konac-hamza
Copy link
Collaborator

@konac-hamza konac-hamza commented Dec 6, 2025

Include system role assignments in the list_for_multiple_actors_and_targets method.

@konac-hamza
Copy link
Collaborator Author

@gtema
The previous commit message cause the lint errors. So i created new PR with clean commit history. Additionally, during workflow building, the PR failed due to OIDC token. The workflow codes may need to be updated to properly handle branches which coming from forked repositories.
Thank you for your support.

@gtema
Copy link
Collaborator

gtema commented Dec 6, 2025

You could have just squashed and rewritten commits, but it's ok. I know that certain workflows require elevated privileges and cannot be executed from forks, but I don't know how to deal with that so far

1 similar comment
@gtema
Copy link
Collaborator

gtema commented Dec 6, 2025

You could have just squashed and rewritten commits, but it's ok. I know that certain workflows require elevated privileges and cannot be executed from forks, but I don't know how to deal with that so far

@konac-hamza
Copy link
Collaborator Author

You could have just squashed and rewritten commits, but it's ok. I know that certain workflows require elevated privileges and cannot be executed from forks, but I don't know how to deal with that so far

I have tried to create new branch from remote repo but remote branch permissions prevent changes on repository. I don't know how to pass tests.

@gtema gtema force-pushed the fix/system-assignments-issue-143-clean branch from bb3392a to dcc480b Compare December 8, 2025 14:54
Include system role assignments in the
`list_for_multiple_actors_and_targets` method.

Closes: openstack-experimental#143
@gtema gtema force-pushed the fix/system-assignments-issue-143-clean branch from dcc480b to 1c6ce57 Compare December 8, 2025 15:03
@gtema gtema linked an issue Dec 8, 2025 that may be closed by this pull request
@gtema gtema changed the title feat: Improve role assignment response structure feat: Include system assignments in the list_for_multiple_actors_and_targets method Dec 8, 2025
@gtema gtema merged commit bebf8c0 into openstack-experimental:main Dec 8, 2025
20 of 22 checks passed
.add_option(
target
.inherited
.map(|x| db_assignment::Column::Inherited.eq(x)),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gtema
I am not sure but there might be a bug in here. during add_option you are using db_assignment but shouldn't it to be db_system_assignment?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yes, you are right. Can you pls make a quick PR for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Role assignments must also include System assignments

2 participants