The DBSchemaApply step's globalSettings field is typed as object only. A runtime expression or string, such as <+stage.variables.globalSettings>, fails pipeline save validation. Sibling fields on the same step (envVariables, delegateSelectors, settings) accept oneOf: [object, string].

Error on save

Stage: db schema deploy — globalSettings: string found, object expected

Expected: globalSettings accepts an expression or string and resolves it to a map at runtime, as the sibling fields do.

Actual: save validation fails with the error above.

Why we need it

Our global_settings comes from a free-form ADF map (Liquibase globals such as log-level and label-filter). It differs per schema and is selected at runtime from the pipeline config matrix. We can't hard-code the keys in the template without losing the ability to pass arbitrary globals.

Request

Change globalSettings to oneOf: [object, string] (matching envVariables and settings) in the step-info schemas above, on both the server-side validation and the published schema.