Skip to content

Document the new ExportBlueprint/ImportBlueprint APIs (2026.1) - #22

Open
nahumtimerman wants to merge 1 commit into
mainfrom
docs/export-import-blueprint-api
Open

Document the new ExportBlueprint/ImportBlueprint APIs (2026.1)#22
nahumtimerman wants to merge 1 commit into
mainfrom
docs/export-import-blueprint-api

Conversation

@nahumtimerman

Copy link
Copy Markdown
Collaborator

Adds a how-to page under DevGuide > CloudShell Automation API > Useful Code Examples for the new ExportBlueprint / ImportBlueprint Automation API methods introduced in CloudShell 2026.1.

The page covers:

  • What the APIs are for: version-controlling blueprint definitions, promoting blueprints between servers, scripted backup.
  • ExportBlueprint — parameters, response shape (Blueprints list of Name/Xml), domain scoping, deterministic output.
  • ImportBlueprint — create-or-update semantics, hard failure when a referenced family/model/attribute/script/driver/category is missing on the target, the active-draft block, and the fact it is deliberately not admin-gated.
  • A runnable Python example (export to file → import into another server) based on the integration-test script.

Grounded in the server implementation (ResourceAPIApplicationService), the Testegator packaging scenarios, and the python-api integration scenario. Also adds the three new API names to the spellcheck wordlist.

🤖 Generated with Claude Code

Adds a how-to for exporting a blueprint as its definition XML and importing
it back - version control, cross-server promotion, backup. Grounded in the
server implementation and the packaging/python-api integration scenarios.

Co-Authored-By: Claude Fable 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.

1 participant