config-migrations

To migrate operator config schemas, run the migration workflow to upgrade all AICP configs to the new schema. It handles key renames, shape changes, deprecations, and new required keys across all config layers.

The AICP config migration process covers default.yaml, profiles/*.yaml, ~/.aicp/config.yaml, and <project>/.aicp/config.yaml. It plans, executes, and validates schema changes across all these deployment layers.

YAML config schema evolution uses in-loader validation and post-migration validation to ensure safe schema changes. It enforces safety checks and provides deprecation warnings to operators during the migration.

Yes, you can migrate AICP configs in-place without breaking deployments. The migration workflow applies deprecation warnings, enforces in-loader validation, and validates post-migration to keep deployments consistent.

The best way to handle deprecated keys and shape changes is using the dedicated AICP migration utility. It automates schema restructuring with safety checks, deprecation warnings, and post-migration validation across all config files.

You need a dedicated migration utility for AICP config schema changes to automate key renames, restructure shapes, and add required keys safely. It enforces validation and provides tooling guidance to verify and complete migrations.