Problem/Motivation

The configuration schema defined in ai_provider_azure.schema.yml does not match the actual structure of the stored ai_provider_azure.settings configuration.

Currently, the schema defines a nested profile key, however, the actual configuration stored by the module has no profile key. As a result, schema validation tools report missing or invalid schema definitions for otherwise valid configuration.

Steps to reproduce

  1. Install and enable the AI Provider Azure module.
  2. Inspect the stored configuration: config:get ai_provider_azure.settings
  3. Compare the configuration structure with the schema defined in ai_provider_azure.schema.yml.
  4. Observe that the schema defines a profile key that does not exist in configuration.

Proposed resolution

I am providing a patch which updates the configuration schema to accurately reflect the configuration structure used by the module:

  • Changes the schema type to config_object
  • Removes the unused profile mapping
  • Defines the top-level data key as a string

This brings the schema in line with the configuration actually written by the module.

Remaining tasks

Review the patch.

User interface changes

API changes

Data model changes

Comments

thefancywizard created an issue. See original summary.

thefancywizard’s picture

Attaching patch.