Skip to content

Problem with defaults not being handled correctly across multiple configuration files #207

@confluence

Description

@confluence

Copied from old Slack discussion. We need to test whether this is still an issue in v5.

JSON schema defaults don’t seem to be used when moving subconfigs to files in 
config.d.  i.e. he hits an error about a missing keyAlgorithm, when the config 
with oidc config specified in config.json depends on the default value on other 
systems.  Not sure if this is an issue with lodash merge or with ajv.  
So apparently when Mike had the controller functioning but still reporting an 
error it was with /etc/carta/config.d/oidc.json and a block in the main 
config.json both in place.  i.e. does seem to confirm an issue loading defaults 
in the files in config.d

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions