feat(sdk): Sync AILAKEHOUSE database type - P002#1326
Open
yenkins-admin wants to merge 1 commit intomasterfrom
Open
feat(sdk): Sync AILAKEHOUSE database type - P002#1326yenkins-admin wants to merge 1 commit intomasterfrom
yenkins-admin wants to merge 1 commit intomasterfrom
Conversation
The AILAKEHOUSE database type support was added to gdc-nas in commits: - b4e5b110d4d818318f462bfa696afbaf30c44635 (merge) - 13cca68ca478fa3574e94ea5ec499dd6289dc08d (implementation) The Python SDK OpenAPI client was already regenerated with the updated metadata-api and scan-model OpenAPI specifications that include the AILAKEHOUSE enum value in commit 796bc68. No additional SDK-specific code changes are required as the AILAKEHOUSE database type is properly handled through the existing SDK infrastructure: - gooddata-api-client models include AILAKEHOUSE in allowed values - SDK validation uses value_in_allowed which checks against client class - All declarative and entity model classes support the new type Related to: CQ-1987, CQ-1899 Problem ID: P002 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
Close please |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Synchronize AILAKEHOUSE database type support from gdc-nas to gooddata-python-sdk.
Jira ticket creation skipped - Jira sandbox under maintenance during workflow run.
Problem ID: P002 - Workflow: https://github.com/gooddata/gdc-nas/actions/runs/22064429506
Summary
The AILAKEHOUSE database type support was added to gdc-nas in commits b4e5b110d4d8 and 13cca68ca478. The Python SDK OpenAPI client was already regenerated with the updated metadata-api and scan-model OpenAPI specifications that include the AILAKEHOUSE enum value.
Changes
Verification
The AILAKEHOUSE enum value is present in:
gooddata-api-client/gooddata_api_client/model/declarative_data_source.pygooddata-api-client/gooddata_api_client/model/json_api_data_source_in_attributes.pygooddata-api-client/gooddata_api_client/model/json_api_data_source_out_attributes.pygooddata-api-client/gooddata_api_client/model/json_api_data_source_patch_attributes.pygooddata-api-client/gooddata_api_client/model/test_definition_request.pySDK validation uses
value_in_allowedwhich checks against the client class's allowed values, ensuring the AILAKEHOUSE type is properly validated.Related Issues
🤖 Generated with automation workflow