PHPerKael Nacos Config
Use this skill for Nacos configuration reads and guarded writes.
Configuration writes can change runtime behavior. Treat them as higher risk than log or database reads.
Required Inputs
Before operating Nacos, identify:
- environment
- namespace or tenant
- group
- dataId
- target key path
- affected workload
- reload or restart requirement
For writes, also identify old value, new value, rollback value, and verification method.
Workflow
- Confirm the target environment and workload.
- Discover actual Nacos settings from workload env or startup config where possible.
- Connect through the approved path for the environment, commonly
kubectl port-forward. - Read the target dataId.
- For writes, snapshot the dataId before editing.
- Make the smallest possible change.
- Publish create, update, or delete only after reviewing the diff.
- Re-read Nacos after publishing.
- Verify runtime effect through workload logs, runtime config endpoint, reload signal, restart, or decisive behavior.
- Report evidence and rollback path.
Safety Rules
- Do not publish config without a snapshot.
- Do not delete a dataId unless deletion is explicitly requested.
- Do not summarize secrets or full credential-bearing config.
- Do not treat successful publish as successful runtime load.
- Do not change unrelated formatting or reorder unrelated keys.
Output
Include:
- environment
- tenant, group, and dataId
- key changed or deleted
- old value summary and new value summary, redacted where needed
- snapshot path
- verification evidence
- rollback path
References
Read commands.md for command templates.