aws_ecs_patterns: add environment parameter to ScheduledFargateTaskDefinitionOptions
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 74
Description
### Describe the feature
Add environment variables parameter to a ScheduledFargateTask like it is possible in ScheduledFargateTaskImageOptions
### Use Case
I want to reuse a task definition for a list of tasks, but also want to hand over a list of environment variables to set it for the containers.
The same is possible in the AWS web console (Scheduled Task->Update->Container overwrites)
At the moment a new task definition is created for each task using the ScheduledFargateTaskImageOptions method.
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.84
### Environment details (OS name and version, etc.)
Amazon Linux 2
Contributor guide
Research direction
Start at the ScheduledFargateTaskDefinitionOptions and ScheduledFargateTaskImageOptions entry points in aws_ecs_patterns, comparing how each accepts container configuration. Trace how ScheduledFargateTask creates task definitions and determine where an environment parameter can be applied. Done means callers can provide environment variables when reusing a task definition without creating a separate definition for each task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100