Thank you for providing such a useful library.
In projects where multiple clusters share the same codebase (e.g., feature, staging environments), the ecschedule.yaml file remains the same. However, when tasks are scheduled, they are registered in Amazon EventBridge without considering the cluster concept. As a result, tasks with the same name within the project get overwritten.
To address this, I would like to propose an option to add a suffix to the task names.
For example, using the following command based on this sample:
https://github.com/Songmu/ecschedule?tab=readme-ov-file#description
ecschedule -conf ecschedule.yaml -taskNameSuffix "_staging" apply -all -prune
This would register tasks with names like taskName1_staging while keeping the yaml file unchanged.
This approach eliminates the need to template the yaml file based on AWS specifications and allows for suffixes to be optional.
What do you think? I appreciate your consideration.
Thank you for providing such a useful library.
In projects where multiple clusters share the same codebase (e.g., feature, staging environments), the ecschedule.yaml file remains the same. However, when tasks are scheduled, they are registered in Amazon EventBridge without considering the cluster concept. As a result, tasks with the same name within the project get overwritten.
To address this, I would like to propose an option to add a suffix to the task names.
For example, using the following command based on this sample:
https://github.com/Songmu/ecschedule?tab=readme-ov-file#description
This would register tasks with names like
taskName1_stagingwhile keeping the yaml file unchanged.This approach eliminates the need to template the yaml file based on AWS specifications and allows for suffixes to be optional.
What do you think? I appreciate your consideration.