Question: Referencing other stacks/Customizing cloudformation output

[nilsga]

I came across this project recently, and I decided to give it a go and convert the "pure" cloudformation based scala lambda project I have. During that process, a couple of questions has arisen:

• Is there a way to references exports from a different cloudformation stack? It would be very handy for exposing other endpoints and services as environment variables, or reference vpc configuration from other stacks.
• Can I add "custom" cloudformation snippets that are inserted into the generated SAM function cloudformation, and other resources (such as custom authorizer configuration, custom swagger api definition etc)?

[dnvriend]

The plugin has been created with a specific feature set I use on a project but it could be a fit for other projects as well.

• Referencing exports from other cloudformation stacks is only supported for a Kinesis Streams Lambda and DynamoDB tables. It uses the import: syntax that encodes the samStage to resolve to a name. Other strategies are not yet supported, although I would like to have an env: expression to look up ARNs from the environment.
• Custom cloudformation snippets are also not supported and needs a design and impact analysis to support this feature.

The project is open to ideas and PRs!