Skip to content

Conversation

@hown3d
Copy link
Member

@hown3d hown3d commented Dec 7, 2025

Description

The current implementation of the project list command does not return all projects a user has permission to see. It just returns the projects a user is directly a member of, not if he inherited the permissions from e.g. an organization or folder.

This PR uses the authorization and resourcemanager APIs to correctly query all projects a user has permission to see.
The implementation is a tree based data structure that uses recursion to view all projects of a folder, nested folders and projects directly under a organization.

For printing the Organization name, as well as the folder path is additionally printed. I decided against querying the resourcemanager API for project details as that returned in 500's from the API if queried to fast.

The existing flag filters do not apply as good anymore to the implementation, so they could be removed if the implementation itself is accepted.

Tests will be implemented once a first review has been done, as this also takes some time. I tested the change manually.

Checklist

  • Issue was linked above
  • Code format was applied: make fmt
  • Examples were added / adjusted (see e.g. here)
  • Docs are up-to-date: make generate-docs (will be checked by CI)
  • Unit tests got implemented or updated
  • Unit tests are passing: make test (will be checked by CI)
  • No linter issues: make lint (will be checked by CI)

@hown3d hown3d requested a review from a team as a code owner December 7, 2025 14:36
@hown3d hown3d changed the title fetch projects by using resource manager tree display projects correctly by using resource manager tree Dec 7, 2025
Signed-off-by: Lukas Hoehl <[email protected]>

split into files

Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
@github-actions
Copy link

This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it.

@hown3d
Copy link
Member Author

hown3d commented Dec 15, 2025

Would love to know your opinion :) @stackitcloud/developer-tools

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.

2 participants