Add config of trackingId

[tomitamasa]

I have tried specifying a trackingId in YAML.

We have a problem when trying to use the -prune option in our project.
Our project has multiple YAML files for the same environment, and when we execute a command with the -prune option, settings from the last apply YAML file overwrite the others.

Related Issue: #92

A trackingId is explicitly specified in a configuration file.

region: ap-northeast-1
cluster: staging
role: ecsTaskExecutionRole
trackingId: test-tag
rules:
...

The EventBridge console

When a trackingId is not specified, the default value is set to the cluster name (ex.staging).
The EventBridge console

this closes #92

[tomitamasa]

@Songmu
Thanks for the nice tool.

Could you please review this Pull Request?
I apologize for the request I made during ISUCON last week.

[Songmu]

Thanks for the pull request!
I see. I understood that it is a need to attach a specific identifier to a job, especially for deletion.
Sorry for the delay in responding, let me give it some thought, including whether naming it trackingID is appropriate.

[tomitamasa]

Thank you for your response!

Applying multiple configuration files at different timings might be less common, but it would be appreciated if you could consider this possibility.

[sinsoku]

What is the status of this pull request?
We are hoping this pull request will be merged as we have the same issue.

I think trackingId is a good and simple name since the AWS tag key is ecschedule:tracking-id.