-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Atlantis init upgrades plugins #1381
Comments
I openned this PR for that #1353. |
you could write a custom workflow to not run init with |
I know I can use a custom workflow to accomplish this, but I feel that predictable and reproducible builds is a very important feature for a CI (/CD) tool like Atlantis. And disregarding the As a reference, you can include the following default workflow in your server-side repo config to stop atlantis from upgrading your plugins: workflows:
default:
plan:
steps:
- init:
extra_args:
- '-upgrade:false'
- plan: or if you use the {
...
"workflows": {
"default": {
"plan": {
"steps": [
{
"init": {
"extra_args": ["-upgrade:false"]
}
},
{
"plan": {}
}
]
}
}
}
} |
I think it should be upgrade=false workflows:
default:
plan:
steps:
- init:
extra_args:
- '-upgrade=false'
- plan: And for {
"workflows": {
"default": {
"plan": {
"steps": [
{
"init": {
"extra_args": ["-upgrade=false"]
}
},
{
"plan": {}
}
]
}
}
}
} The above does work for us |
closed by #1651 |
Atlantis runs terraform init with the
-upgrade
option. This upgrades plugins even if I've checked in the.terraform.lock.hcl
file.The workaround is to lock the plugins in
terraform
required_providers
, but this should not be necessary. Even if I've requested a range of versions of a plugin, Atlantis should respect the.terraform.lock.hcl
file.The current Atlantis behavior causes non-repeatable builds when using version ranges for providers, which is exactly what the lock file was supposed to prevent.
Terraform version 0.14.4
Atlantis version 0.16
The text was updated successfully, but these errors were encountered: