- Le plus récent
- Le plus de votes
- La plupart des commentaires
To help you with your query, I created one similar EventBridge rule and target using the code you provided(with modifications to deploy it in my account).
Once the rule got created, I created a commit into one of my CodeCommit repositories and then created one git tag
I used below mentioned commands to create the git tag
$ git tag release-test cf488685
$ git push origin release-test
Here, cf488685 is the shorter version of the full commitId (cf488685bfd6f8d4f6def8e985a3648b18333d3e)
Once the git tag was created, I checked the lambda function logs and it received the commitId cf488685bfd6f8d4f6def8e985a3648b18333d3e. So, the configuration that you've used in CDK is correct. To be specific, here $.detail.commitId
is the full commitId of the commitId that we used while creating git tag (if we specified shorter version). Therefore, please check if the commitId that you're noticing is the full version of the id that you specified while creating git tag.
If you have a support plan with your account, then you can reach out to us creating a support case from the Support Center
as well.
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 8 mois
- AWS OFFICIELA mis à jour il y a 4 mois