permission-model-change-guide

Standardize and automate IAM RBAC changes for new resource types.

2.5k|521|Updated May 29, 2019

Ready to run

npx skills add https://github.com/TencentBlueKing/bk-ci --skill permission-model-change-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: permission-model-change-guide
Source: https://github.com/TencentBlueKing/bk-ci/tree/main/ai/skills/permission-model-change-guide
Command: npx skills add https://github.com/TencentBlueKing/bk-ci --skill permission-model-change-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a reusable, standard process for integrating new IAM RBAC resource types, including resource type definitions, instance selections, actions, and migration scripts, to ensure consistent permission governance across projects.

Core Features & Use Cases

Defines a standard workflow for resource type onboarding: resource type, instance selection, actions, groups, and migration steps.
Describes how to migrate permissions for new resources, configure IAM callbacks, and migrate data safely.
Applicable to teams adding new resources, updating permissions, or migrating existing models in enterprise IAM.

Quick Start

Follow the steps to adapt the creative_stream access patterns for a new resource type, including updating enum, JSONRBAC definitions, and initial SQL.

Frequently Asked Questions about permission-model-change-guide

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

FAQPage Schema

How do I standardize IAM RBAC changes when integrating new resource types?▼

To standardize IAM RBAC changes for new resource types, apply a structured workflow covering resource type definitions, instance selectors, action definitions, groups, and SQL/API change options. This ensures consistent permission governance across projects.

What is the standard process for migrating permissions for new resources in enterprise IAM?▼

The standard process for migrating permissions for new resources involves defining resource types, configuring instance selections, setting up actions, and executing migration scripts. This approach guarantees safe data migration and consistent permission updates across enterprise IAM projects.

How do I configure IAM callbacks and migrate data safely for new resource types?▼

To configure IAM callbacks and migrate data safely for new resource types, follow the defined resource type onboarding workflow. It includes updating enum and JSONRBAC definitions, applying initial SQL scripts, and handling API change options for secure data transitions.

Can I use this guide to update permissions and migrate existing models in enterprise IAM?▼

Yes, you can use this guide to update permissions and migrate existing models in enterprise IAM. It applies to teams adding new resources, updating permissions, or migrating existing models by providing a reusable, standard process for integrating new IAM RBAC resource types.

Does the guide provide step-by-step instructions for updating enum and JSONRBAC definitions?▼

Yes, the guide provides step-by-step instructions for adapting access patterns for a new resource type. It specifically covers updating enum and JSONRBAC definitions, along with applying initial SQL scripts to ensure a structured permission migration.

What are the limitations of applying a standard workflow for IAM RBAC resource type onboarding?▼

The guide focuses on standardizing IAM RBAC changes for new resource types, instance selections, actions, and migration scripts. It enforces a structured workflow with SQL/API change options, so it may not cover highly customized, non-standard permission models outside this specific scope.