Provide documentation for managing copilot files with multiple repositories

It seems there is a gap in explaining how the copilot files are best managed in a multi-repo scenario.
If you have services in multiple repos, you won't want to duplicate your copilot env manifests, so I'm assuming a separate infra repo is the answer.
But to access the containers, you will need to either:

• Build docker images from individual service repos into ECR, and then hand off to the infra repo to deploy, passing along the image to use. But copilot commands don't seem to support just the ECR upload step alone.
• Move or copy dockerfiles into the infra repo (Neither sounds good)
• Checkout the service repos to gain access to the dockerfiles, or else curl the dockerfiles from Github.

I'm not sure why this is not addressed in the docs. The various walkthroughs online conveniently assume all your services are in the same repo.

[KollaAdithya]

Hello @ryan-nookly!
Thank you for this issue. I will label this as documentation for improving our documentation on managing files in multiple repos.

Copilot allows you to create pipeline both for Environments or workloads.

  What type of continuous delivery pipeline is this?  [Use arrows to move, type to filter, ? for more help]
  > Workloads           (Deploy the services or jobs in your workspace)
    Environments        (Deploy the environments in your workspace)

Suppose in repo A you can have only the environment manifests in your pipeline and deploy the infrastructure for your environment.

Repo A # only env manifest in Repo A
|- copilot
  |- .workspace
  |- environments

With out duplicating env manifests in each individual Service Repositories.
For example

Repo B  # RepoB for frontend service with out any environment manifest. 
|- FrontendSvc
  |- copilot
    |- .workspace
    |- frontend
      |- manifest.yaml
  |- Dockerfile
  |- src

In Repo C you can have another service such as backend.

Repo C  # RepoC for backend service with out any environment manifest. 
|- BackendSvc
  |- copilot
    |- .workspace
    |- backend
      |- manifest.yaml
  |- Dockerfile
  |- src

Thanks for the detailed reply @KollaAdithya!
I see that it works for manual CLI deployments as well. You go into each service repo to deploy it.