update-stack

Regenerate the deployment zip and update an existing ORM stack.

3|2|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill update-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-stack
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/update-stack
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill update-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebuilds the deployment artifact and updates an existing ORM stack with the latest code changes, reducing manual deployment effort and drift.

Core Features & Use Cases

  • Artifact Rebuild: Regenerate the deployment zip from the current codebase.
  • Stack Update & Plan: Trigger OCI Resource Manager to update the stack and poll for plan completion.
  • Profile & Safety: Prompt for OCI CLI profile selection if not preset and log changes for audit.

Quick Start

Regenerate the deployment zip from the current codebase and trigger a stack update for the given ORM stack OCID.

Frequently Asked Questions about update-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an OCI Resource Manager stack with new Terraform code?

To update an OCI Resource Manager stack, you must regenerate the deployment zip from your current codebase and trigger a plan-driven stack update using a target stack OCID. This process automates artifact rebuilding and polling for plan completion.

What is the best way to rebuild a deployment zip for an existing ORM stack?

The best way to rebuild a deployment zip for an ORM stack is to use an automation tool that regenerates the artifact from the current codebase and directly triggers the OCI Resource Manager update, reducing manual deployment effort and configuration drift.

Why does my OCI Resource Manager stack update fail without a configured CLI profile?

An OCI Resource Manager stack update requires a configured OCI CLI profile to authenticate and trigger the plan. If a profile is not preset, the update process cannot execute and will prompt for manual profile selection.

What are the limitations of automating ORM stack updates with Python tooling?

Limitations include the strict dependency on having Python tooling configured and a valid OCI CLI profile preset. The process specifically targets artifact regeneration and plan-driven updates, meaning it may not cover manual apply stages or non-Terraform deployment methods.