Skip to content

feat(studio): support deployment resource configuration - #843

Merged
yaozheng-fang merged 4 commits into
volcengine:mainfrom
evanlowe:feat/studio-deployment-resource-config
Aug 8, 2026
Merged

feat(studio): support deployment resource configuration#843
yaozheng-fang merged 4 commits into
volcengine:mainfrom
evanlowe:feat/studio-deployment-resource-config

Conversation

@evanlowe

@evanlowe evanlowe commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a Resource Configuration section before environment variables on the final deployment page
  • support automatic creation, custom names, and existing-resource selection for TOS, CR, and CodePipeline
  • show generated automatic resource names and provide searchable existing-resource selectors with infinite-scroll pagination
  • persist resource metadata in Runtime tags so in-place updates reuse the original resources while keeping resource controls hidden during updates
  • keep legacy Runtime updates compatible when resource tags are absent
  • support both Volcengine and BytePlus resource APIs and credential environments
  • preserve original deployment and resource-loading errors while redacting credentials
  • align resource fields and remove the gray fill from deployment configuration cards

Dependency

Requires agentkit-sdk-python#163 for resource-listing APIs and custom build-resource handling.

Testing

  • pre-commit hooks: Ruff check, Ruff format, and gitleaks
  • frontend tests: 424 passed
  • frontend production build: passed
  • full Python test suite: 1277 passed, 6 skipped, 6 subtests passed
  • local provider deployment matrix: 27 Volcengine combinations and 27 BytePlus combinations passed
  • real Volcengine deployments verified with existing resources, named TOS creation, named and automatic CodePipeline creation, automatic TOS selection, and Runtime in-place update
  • real BytePlus deployment verified with existing TOS, CR, and CodePipeline resources, followed by Runtime version 1 to 2 in-place update using the same Runtime ID and resources
  • temporary BytePlus Runtime was removed and verified absent after testing

Known limits

  • the Volcengine validation account had exhausted CR repository and Micro instance quotas, so automatic and named CR creation were rejected by the cloud service; those request paths are covered by provider tests
  • the cloud-hosted Studio IAM replay still requires an authorized Identity login; direct real-cloud resource validation completed successfully

@evanlowe evanlowe changed the title feat(studio): configure deployment cloud resources feat(studio): support deployment resource configuration Aug 8, 2026
@yaozheng-fang
yaozheng-fang merged commit d5e0070 into volcengine:main Aug 8, 2026
7 checks passed
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