iam-migration-validation

Automate post-migration validation between ETBC and IAM with Python scripts.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/LLLLimbo/Skills --skill iam-migration-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iam-migration-validation
Source: https://github.com/LLLLimbo/Skills/tree/main/goldcard-specified/iam-migration-validation
Command: npx skills add https://github.com/LLLLimbo/Skills --skill iam-migration-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates repeatable validation to ensure ETBC-to-IAM migrations preserve login capability, permission parity, and correct app/menu mappings across IAM components such as iam-management-service, iam-auth-center-service, APISIX, and portal-front.

Core Features & Use Cases

  • Automated baseline extraction and cross-system comparisons to verify user logins, roles, permissions, and resource trees.
  • Per-tenant validation with diff reporting to support release gates and traceability.
  • End-to-end portal checks and automated reports guiding remediation and validation workflows.
  • Script-driven validation using the included tools: validate_legacy_mappings.py, compare_menu_tree.py, compare_role_permissions.py, portal_login_smoke.py.

Quick Start

Run the validation workflow using the included scripts to compare ETBC baseline data against IAM mappings and produce a summary in your chosen output directory.

Frequently Asked Questions about iam-migration-validation

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

FAQPage Schema
How do I validate permissions parity after an IAM migration?

You can automate post-migration validation using Python scripts that verify login compatibility, permissions parity, and app menu mappings per-tenant, aggregating baseline data from SQLs and portal endpoints to generate diff reports and release gates.

How do I verify login compatibility and portal mappings post-migration?

You can automate post-migration validation using Python scripts that verify login compatibility, permissions parity, and app menu mappings per-tenant, aggregating baseline data from SQLs and portal endpoints to generate diff reports and release gates.

Can I generate per-tenant diff reports for ETBC to IAM migrations?

Yes, you can generate per-tenant diff reports by running validation scripts that compare legacy mappings and menu trees against IAM endpoints, enforcing data integrity and authentication checks to produce structured summaries for release gates.

What is the best way to automate app and menu tree comparisons for IAM?

The best way to automate menu tree comparisons for IAM is using the compare_menu_tree.py script, which cross-references baseline data against IAM portal endpoints to identify discrepancies in app and menu mappings.

Do I need Python to use this IAM migration validation workflow?

Yes, you need Python to execute the provided validation scripts such as validate_legacy_mappings.py, compare_menu_tree.py, compare_role_permissions.py, and portal_login_smoke.py to run the automated validation workflow.

Why does my post-migration portal login smoke test fail for specific tenants?

Your portal login smoke test may fail due to authentication or authorization mismatches between ETBC and IAM endpoints; the validation scripts enforce data integrity checks to help identify and remediate these per-tenant discrepancies.