Skip to content

Make profiles resolve recursively? #19

@iku000888

Description

@iku000888

Old behavior of :duct.core/include key

config foo.edn

{:foo/foo 1}

config bar.edn

{:bar/:bar 2
 :duct.core/include ["foo.edn"]}

config.edn that includes bar.edn

{:duct.core/include ["bar.edn"]}

And prep'ing config.edn would result in

{:foo/foo 1
 :bar/bar 2}

Trying something similar with #duct/include

#duct/include assumes the expanded config map will be under a profile key, so simple replacing :duct.core/include with #duct/include will not do.

e.g.

config foo.edn

{:foo/foo 1}

config bar.edn

{:bar/bar 2
 #duct/include "foo.edn"}

config.edn that includes bar.edn

{:some/profile #duct/include ["bar.edn"]}

does not recursively resolve.

Some more contexts from slack convo

selection_146

selection_147

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions