Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to set SQS queue policy on experimental workflow_job_events_queue #3882

Open
joemiller opened this issue Apr 30, 2024 · 0 comments
Open

Comments

@joemiller
Copy link

The enable_workflow_job_events_queue var allows for setting up an extra SQS queue where a copy of each webhook payload is copied. The docs list this as experimental with potential use cases being for gathering metrics, responding to matrix builds, etc. Basically whatever extra things the user may need to integrate.

In my case I have been using a logs+metrics exporter that consumes the queue. In my case this exporter runs in an EKS cluster in a separate AWS account. I had been using an aws_sqs_queue_policy to allow the external principal to consume the queue.

This recent change - a8cba4e - broke my configuration, however, because this policy overwrites the one I lay down via another terraform stack.

I think I can work around this by creating an IAM role in the account containing the SQS queue and assuming this role from my consumer in the other AWS account. However, it would be useful to provide an extra var in this stack so that users could add their own queue-policy statements. Since this queue is not used internally by the runner stack and is meant for users to build their own additional functionality this seems like a reasonable request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant