Copilot-cli: feature: add support for environment specific addons

[noahjahn]

It would be awesome to be able to have AWS resources created for services to share within a single environment.

Use case

I have two services running as part of each environment in my copilot application. Both services required a PostgreSQL database. Instead of creating a RDS instance for each service, I would like to have a single RDS instance for the environment that either of the two services could reference different databases in.

[sharepointoscar]

I might be reading your feature request incorrectly, but doesn't this satisfy your need to deploy additional resources? https://aws.github.io/copilot-cli/docs/developing/additional-aws-resources @noahjahn

[noahjahn]

I might be reading your feature request incorrectly, but doesn't this satisfy your need to deploy additional resources? https://aws.github.io/copilot-cli/docs/developing/additional-aws-resources @noahjahn

I think this could work, I just thought it'd be a cool to not tie the add on to a specific service but rather at a higher level.

[efekarakus]

Hi @noahjahn ! Not quite a solution but this comment: https://github.com/aws/copilot-cli/issues/1368#issuecomment-692316027 might be of interest for you.

The idea is to create a resource tied to a particular service in the addons stack, and then "export" any interesting values as SSM parameters so that they can be injected as environment variables in other services. While it's not ideal, it's a work around for now.