Epic: Document Advanced Dependencies

[carolynvs]

Start a new page to document how dependencies v2 work (conceptual docs, task, etc) but flag that it's not implemented yet. Do not update the existing page since that needs to stay the same to support the current implementation.

TODO: Split these into separate issues

• Update CNAB Support Page with Dependencies v2
• Concept Doc: Dependencies
  • Include use cases and pictures and yaml snippets from the proposal
• Concept Doc: Bundle Interfaces
  • mention well-known interfaces and link
  • Link to provider independent bundles
• Concept Doc: Bundle Composition
  • meta bundles
• Concept Doc: Solve Bundle Dependency Graph
  • Should the docs that go into implementation details be reference docs?
• Concept Doc: Workflows
• Concept Doc: Execution Plans
• Concept Doc: Well-Known Bundle Interfaces
  • link to task for multi-provider bundle (wordpress)
• Concept Doc: Multi-cloud Bundles
  • pick a name and stick with it: provider independent, multi-provider, generic bundles... whatever
• Task Doc: Depend on another bundle
  • graph
  • default implementation
  • passing data
• Task Doc: Install a bundle on multiple cloud providers
  • provider independent bundles
  • bundle interfaces
  • wordpress bundle example with redis, k8s and mysql
• Task Doc: Move a bundle across an airgap
  • the existing doc at https://getporter.org/administrators/airgap/ is a concept doc and should be moved
  • Update existing doc with info about how deps are moved and relocated, including bundle interfaces, default implementations
  • Include in the task doc moving a simple bundle and a bundle with dependencies that have default implementations
• Example Doc: Deploy Bundles with Generic Dependencies in an Airgapped Environment
  • Wordpress example bundle
  • Make a new example bundle that has dependencies with default implementations (voter app)

ℹ️ Read PEP003 - Advanced Dependencies for context about how dependencies should work, design details, and notes about desired behavior.