search

Azure / draft-classic

A tool for developers to create cloud-native applications on Kubernetes.
https://draft.sh
MIT License
3.92k stars 397 forks source link

Usage with monorepos #902

Open gaui opened 5 years ago

gaui commented 5 years ago

How would you use Draft with monorepos where all dependencies are managed at the root-level by some dependency manager like Paket / Lerna / etc.

Project structure might look something like this:

/
|-- .paket
|-- paket.dependencies
|-- Project_1
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>
|   `-- Client
|       `-- Dockerfile
|       `-- lerna.json
|   |   `-- <project files>
|-- Project_2
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>
|   `-- Client
|       `-- Dockerfile
|       `-- lerna.json
|   |   `-- <project files>

To be able to build the API in Project_2 I would need this build context:

/
|-- .paket
|-- paket.dependencies
|-- Project_2
|   |-- API
|   |   |-- Dockerfile
|   |   `-- paket.references
|   |   `-- <project files>

Is there some way to specify additional files with draft create command? What is the best way to achieve this?