Design: Dependency Graph Traversal

[carolynvs]

Currently we only resolve dependencies down a single level. Eventually more complicated bundles will want to have dependencies that have dependencies too. Resolve and apply them from the bottom up.

[glyn]

By nested dependencies do you mean anything other than transitive dependencies? The use of a different term made me wonder.

I haven't discovered how dependencies are specified in Porter (I spent at least 5 minutes scanning the code ;-) ), but have you any thoughts about the approach you might take on dependency resolution? See this and this for example.

[carolynvs]

D'oh! You caught me out, I didn't use the official term. 👀 I've updated the title to reflect what I meant (transitive dependencies, aka dependencies of my dependencies). Right now porter doesn't traverse the dependency graph and only resolves direct dependencies.

Yup, I've seen from maintaining dep the many ways that dependency management and resolution are hard which is why we stopped at direct dependencies for the moment while we are focused on the POC and developer experience for authoring bundles.

Here is an example of dependencies in porter:

https://github.com/deislabs/porter/blob/55e259ce57aabb7138c28668210f6dbfcc0243a0/build/testdata/bundles/wordpress/porter.yaml#L8-L12

[glyn]

Thanks @carolynvs. I've raised #147 to discuss dependencies further (still waiting for slack access).

[carolynvs]

I dunno if it's a glitch in the matrix or what? I got immediate access through this form: https://slack.cncf.io

[carolynvs]

Closing. This will be implemented through PEP 003.