Skip to content

feat(gooddata-sdk): [AUTO] add exclude_user_settings parameter to workspace settings methods#1332

Open
yenkins-admin wants to merge 1 commit intomasterfrom
feature/auto-P008-add-exclude-user-settings-param
Open

feat(gooddata-sdk): [AUTO] add exclude_user_settings parameter to workspace settings methods#1332
yenkins-admin wants to merge 1 commit intomasterfrom
feature/auto-P008-add-exclude-user-settings-param

Conversation

@yenkins-admin
Copy link
Contributor

Added optional exclude_user_settings parameter to SDK wrapper methods for resolving workspace settings.

Problem ID: P008
Workflow: https://github.com/gooddata/gdc-nas/actions/runs/22096000751

Changes in gdc-nas

Commit 8ce1041a4836c36dd86607c60b0f72d3066e5bd9:

  • Added excludeUserSettings query parameter (boolean, default false) to all four settings resolution endpoints
  • When true, user-level settings are excluded from resolution, skipping the user layer in the hierarchy
  • Modified SettingController, SettingAuthorization, SettingProvider, and MetadataStoreGrpcService
  • Updated OpenAPI spec to reflect the new parameter

SDK Implementation

Added optional exclude_user_settings parameter (bool, default False) to SDK wrapper methods in CatalogWorkspaceService:

  • resolve_all_workspace_settings
  • resolve_workspace_settings

This parameter is passed through to the underlying API client methods, allowing SDK users to exclude user-level settings from resolution.

Files Modified

  • packages/gooddata-sdk/src/gooddata_sdk/catalog/workspace/service.py

JIRA: TBD (Jira sandbox under maintenance)
Risk: Low

…kspace settings methods

Added optional 'exclude_user_settings' parameter (bool, default False) to:
- CatalogWorkspaceService.resolve_all_workspace_settings
- CatalogWorkspaceService.resolve_workspace_settings

This allows SDK users to exclude user-level settings from resolution,
matching the new functionality available in the underlying API client.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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