Init commands

Goal: To allow updating of dependencies in a safe way even when multiple replicas are being used.

1. Ability to execute arbitrary commands within the context of a service, meaning you have access to all the configuration setup by Tye to be able to communicate with dependencies if needed.
2. Ability to create pre-canned, named, commands that will automatically appear as UX in the dashboard for you to invoke as-needed.
3. option to automatically execute a command. Automatically executed commands mean we need to do startup in at least this order:
   1. Start all dependencies
   2. Run all init scripts in parallel
   3. Start all services.

strawman example:

name: VotingSample
services:
- name: worker
  project: worker/worker.csproj
  init:
    - name: migrate
      cmd: "dotnet ef migrate"
- name: postgres
  image:  postgres
  env:
  - name: POSTGRES_PASSWORD
    value: "pass@word1"
  bindings:
  - port: 5432
    connectionString: Server=${host};Port=${port};User Id=postgres;Password=${env:POSTGRES_PASSWORD};

[xavidram]

@tungphuong While we wait for the Tye team to integrate this feature. For now there is not much else you can do other than serve your database containers independently through a docker compose file binding a command in the docker compose, then serve the Tye services. After the Database containers have been spun up.

[esskar]

Are there any updates to this?