Allow read-only AWS integrations to be autoattached

We have separate AWS IAM roles for Spacelift integration attachments, so we can allow preview runs to run on unapproved code changes, without worrying about someone being able to make a change to the underlying AWS resources from their GitHub branch.

This is working well, except autoattach:<label> no longer works to attach these integrations, because it defaults to allowing writes. So we have to explicitly create every integration attachment for every stack.

Is it possible to allow autoattach_read:<label> (and autoattach_write:<label> for symmetry) labels on AWS integrations to specify what the integration should be used for on the stacks that match?

Workaround
We can manually specify multiple integration attachments for every stack
Problem
We want to ensure that previews are not executed with AWS write permissions, to ensure that unapproved code cannot modify the AWS resources.

Please authenticate to join the conversation.

Upvoters
Status

πŸ‘€ In Review

Board

πŸ’‘ Feature Requests

Tags

Integrations

Date

About 2 hours ago

Subscribe to post

Get notified by email when there are changes.