Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow yaml / json objects in config files for #1039

Merged
merged 1 commit into from
Jun 13, 2024
Merged

feat: allow yaml / json objects in config files for #1039

merged 1 commit into from
Jun 13, 2024

Commits on Jun 13, 2024

  1. feat: allow yaml / json objects in config files for

    encrypted_passwords
    plan definitions
    provision defaults and other overrides in services
    currently csb expects
    
    service.something.plans to be a STRING. The code will do some manual deserializing and would fail if that path in the yaml / json config didn't contain a string.
    
    This adds support for using real json / yaml objects to configure the csb app.
    In the current deployment process of csb via a Tile, multiple layers of config are rendered and ensuring that (e.g. plans) value stays a string is convoluted and error prone. We should just allow using actual objects instead of expecting string representations of objects..
    
    add comments for helper functions to access viper config
    
    [#187498188]
    nouseforaname authored and blgm committed Jun 13, 2024
    Configuration menu
    Copy the full SHA
    e248f81 View commit details
    Browse the repository at this point in the history