Skip to content

feat(sdk): DX-PENDING - Document storage_ids validation requirement#1323

Open
yenkins-admin wants to merge 1 commit intomasterfrom
feature/auto-P003-fix-storage-ids-validation
Open

feat(sdk): DX-PENDING - Document storage_ids validation requirement#1323
yenkins-admin wants to merge 1 commit intomasterfrom
feature/auto-P003-fix-storage-ids-validation

Conversation

@yenkins-admin
Copy link
Contributor

Updated API client documentation to clarify that storageIds must not be empty when provisioning AI Lake database instances.
Jira ticket pending (sandbox in maintenance): Document storage_ids validation for AI Lake provisioning
Problem P003: Fix storage IDs in AI Lake provision request model and controller - Workflow: https://github.com/gooddata/gdc-nas/actions/runs/22064429506

Changes

  • Updated ProvisionDatabaseInstanceRequest.md to document that storage_ids must not be empty
  • This reflects backend validation added in gdc-nas (commits ba71f5a and c8da410) that validates storageIds parameter

Background

The backend now validates that storageIds must be provided and must not be empty when provisioning AI Lake database instances (CQ-1968). This change ensures the API documentation accurately reflects this requirement.

Testing

Documentation update only - no code changes to test. The API client model already properly supports the storage_ids field.

🤖 Generated for Problem P003

The backend now validates that storageIds must not be empty when
provisioning AI Lake database instances. Updated API documentation
to reflect this requirement.

Related to P003: Fix storage IDs in AI Lake provision request model and controller

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@tychtjan
Copy link

Close please -> I let agent loose :D

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