Terraform: Better integration with non-chalice managed resources
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
When using Terraform support, I'd like to see the ability to better integrate a chalice application with non-chalice resources. For example, if I create an SQS queue in Terraform, it would be nice to be able to define some variables in the `chalice.tf.json` file that could be referenced by, say, the environment variables passed to the Lambda function. Conversely, if I need to reference the ARN of a function from my non-chalice Terraform, I'd like to be able to augment the outputs with that information. (e.g. to integrate with Event Bridge, which isn't supported yet)
Contributor guide
Research direction
Start by reviewing Chalice's Terraform support and the generated chalice.tf.json configuration. Trace how Lambda environment variables and Terraform outputs are currently represented, then define what is needed for references to non-Chalice resources such as SQS and for exposing function ARNs to external Terraform; done means both integration directions are supported without EventBridge-specific assumptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100