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

Question: How to avoid drift in AMI IDs #4460

Open
dgokcin opened this issue Mar 7, 2025 · 0 comments
Open

Question: How to avoid drift in AMI IDs #4460

dgokcin opened this issue Mar 7, 2025 · 0 comments

Comments

@dgokcin
Copy link

dgokcin commented Mar 7, 2025

Hello and thank you for this great project. I have the following multi-runner configuration where I use an AMI by runs-on since they are really close to the GitHub Actions runners and are updated regularly. One thing I have noticed is once the terraform module is applied, if the ami-id is deleted by the ami provider, the builds get stuck. And I need to re-apply the module to update the id in the launch template.

Is there a way to make this more dynamic or easier to maintain?

Thanks!

        #... multi_runner_config  
        enable_runner_binaries_syncer = true
        ami_owners                    = ["135269210855"] # runs-on ami account id

        userdata_template             = "./templates/user-data-runs-on.sh" #userdata for runs-on
        ami_filter = {
          name  = ["runs-on-v2.2-ubuntu24-full-x64-*"],
          state = ["available"]
        }
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