canonical / canonical/cloud-init

[enhancement]: Distinguish between genuine schema errors and deprecated keys

Open
#5,405 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

At present, all issues with schemas are documented in the log file with a warning and log stating the config is invalid. In some cases, the the only problem with the schema is a deprecated key. Per GH-5404, the current warning/log can be alarming to users and wastes their time when they have to go check their schema only to learn that the invalid log just meant a deprecated key. If the schema validation code returned a different values for deprecated keys vs true invalidity, we could log those results differently at appropriate levels.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.