Skip to content

fix: Allow additional EFS volumes without enable_efs=true #413

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

Conversation

armyers
Copy link

@armyers armyers commented Feb 13, 2025

This is required to allow mounting any arbitrary paths for atlantis features like team_authz, or webhooks, without needing to set enable_efs=true. These are settings that are global so they should not be part of any particular github repo that uses atlantis.

Description

Only required modifying on line in main.tf to allow additional volumes if the volume name is not "efs"

Motivation and Context

My use-case is that I need to add a team_authz script to control permissions for who can run TF apply on prod deployments. The script cannot go in a specific repo, and I didn't want to build it into a custom atlantis image. This fixes issue #408 .

Breaking Changes

None.

How Has This Been Tested?

I've tested it in our company environment and it works great.

…efs=true

This is required to allow mounting any arbitrary paths for atlantis features
like team_authz, or webhooks. These are things that are global settings so
they should not be part of any particular github repo that uses atlantis.
@armyers armyers changed the title fix(ecs_service.volume): allow additional EFS volumes without enable_efs=true Allow additional EFS volumes without enable_efs=true Feb 13, 2025
@armyers armyers changed the title Allow additional EFS volumes without enable_efs=true fix: Allow additional EFS volumes without enable_efs=true Feb 13, 2025
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Mar 16, 2025
Copy link

This PR was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this Mar 27, 2025
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant