add-operator

Extend AWS CloudFormation with force-deletion logic for failing resource types.

91|3|Updated Jun 19, 2022
One-click install
npx skills add https://github.com/go-to-k/delstack --skill add-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-operator
Source: https://github.com/go-to-k/delstack/tree/main/.claude/skills/add-operator
Command: npx skills add https://github.com/go-to-k/delstack --skill add-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need to support force-deletion for CloudFormation resource types that typically cause DELETE_FAILED. It provides mechanisms to automatically detach, delete, or otherwise unblock resources, enabling seamless stack removal.

Core Features & Use Cases

  • Add support for new resource types that require specific force-deletion operations, like clearing buckets or detaching dependencies.
  • Automate complex cleanup tasks involving various AWS services, ensuring reliable stack deletions.
  • Use Case: When a new AWS resource type, such as AWS::IAM::User, consistently causes deletion failures due to attached policies or dependencies, this Skill helps developers implement custom force-delete logic to resolve the issue.

Quick Start

Use this Skill to add support for a new resource type by providing the resource's AWS SDK operations necessary for force deletion.

Frequently Asked Questions about add-operator

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

FAQPage Schema
How do I force delete AWS CloudFormation resources that cause DELETE_FAILED stack errors?

To force delete CloudFormation resources causing DELETE_FAILED errors, you can implement custom operators that automatically detach or delete dependencies like attached IAM policies, enabling seamless stack removal.

What is the best way to automate cleanup for AWS resources with complex dependencies?

Automating cleanup for AWS resources with complex dependencies involves extending CloudFormation with custom force-deletion logic that manages resource dependencies effectively through SDK integration and validation.

How do I add support for new AWS resource types requiring specific force-deletion operations?

You add support for new AWS resource types by providing the necessary AWS SDK operations for force deletion, allowing the system to automatically unblock resources like clearing S3 buckets or detaching dependencies.

Can I use custom operators to handle CloudFormation deletion failures for IAM users?

Yes, custom operators can handle CloudFormation deletion failures for IAM users by implementing force-delete logic to resolve issues like attached policies or dependencies that consistently cause deletion failures.

Why does CloudFormation stack deletion fail and how can custom deletion logic resolve it?

CloudFormation stack deletion fails when resources have attached dependencies or policies, but custom deletion logic resolves this by automatically detaching, deleting, or unblocking resources to ensure reliable stack removal.

Do I need AWS SDK integration to implement force-delete logic for CloudFormation resources?

Yes, AWS SDK integration is required to implement force-delete logic, as it provides the operations necessary to manage resource dependencies, generate code, and validate the complex cleanup tasks.