It would be great to have env and meta_data properties in amazon eventbridge events to avoid calling Buildkite API to obtain those properties.
Hello 
I have raised this with the product team to review further for you. In the meantime, please can you provide more context on how the absence of the env and meta_data properties is currently impacting your workflow. Overall just looking for more context on this and its impact on your end so we can add to the review. Thanks
Also wanted to add here that Eventbridge had size limits on payloads, and a large env or meta-data object could exceed those limits and cause problems. However, I believe these limits have been recently updated on the AWS side so will also review that point on our end.
We store some custom info related to our builds in env/meta_data that is used for dashboards/alerts. If we have many concurrent builds calling the Buildkite API to get info (env/meta_data) not present in the event payload, we can hit the API limit.
Hey @kuri-benchling that’s interesting, how often are you seeing issues with API rate limiting? I’d be keen on taking a look more in to this for you, so if you’d like to email instead so that we can look at specific builds then you’re welcome to at support@buildkite.com
As mentioned above, there are limits on the payload we can provide via EventBridge, so we’d likely face issues in providing both env and metadata via those events. I’m wondering if there might be alternatives we can look at here, or what kind of API volume we’re looking at; this isn’t something we’ve seen much issue with in the past.
Cheers!
We were hitting API rate limit daily. We have change our process to call the API retrieving env and metadatafor only events that we need. It seems to be fine now - we don’t hit the rate limit any more. I understand about EventBridge payload limits - it is valid concern. We can close this issue.