aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Support for creating/updating a trigger to 'ACTIVATED' state (and deactivating to 'CREATED')
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Glue::Trigger
### Resource name
_No response_
### Description
Although there is an option to use 'start_on_creation' to ACTIVATE a trigger [link](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-glue-trigger.html#cfn-glue-trigger-startoncreation), it does not work for already deployed triggers that we want to update.
The current property 'start_on_creation' activates an trigger and starts it (im not sure if at deployment/creation time or at scheduled time -> if the latter then the name is not good). The problem is quite often we need to DEACTIVATE and then ACTIVATE a trigger and thats then not possible when the trigger already exists.
Hence it would be great to have an API that covers this scenario:
- deactivate an TRIGGER
- activate (not only create) on update/create to be run at scheduled time.
Because we uce CDK / CF the cli commands are not enough for us [link](https://docs.amazonaws.cn/en_us/glue/latest/dg/activate-triggers.html)
aws glue start-trigger --name MyTrigger
aws glue stop-trigger --name MyTrigger
### Other Details
In my project we use IAC tools (cdk) to mange glue and thats a problem for us - we cant update an created trigger (without startoncreation set on creation time) to e.g. disable an trigger (of type schedule) or activate it.
Contributor guide
Research direction
Start with the AWS::Glue::Trigger resource and the existing start_on_creation property, then review the linked CloudFormation and Glue documentation. Define how updates should transition triggers between CREATED and ACTIVATED states, including deactivation, and verify that the behavior works for both create and update operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100