JT
06/27/2023, 5:01 PM<http://registry.terraform.io/oracle/oci|registry.terraform.io/oracle/oci>: failed to instantiate provider "<http://registry.terraform.io/oracle/oci|registry.terraform.io/oracle/oci>" to obtain schema: timeout while waiting for plugin to start
Keeps happening, could it be due to the fact I have multiple projects that rely on this provider running at once?JT
06/27/2023, 5:33 PMJustin S
06/27/2023, 5:34 PMJustin S
06/27/2023, 5:34 PMJustin S
06/27/2023, 5:34 PMthing
we get an issueJT
06/27/2023, 5:35 PMJT
06/27/2023, 5:38 PMparallel_apply: false
, it works nowJT
06/27/2023, 5:40 PMJT
06/27/2023, 6:33 PMwby
06/28/2023, 6:09 PMChastity Blackwell
06/29/2023, 6:42 PMundiverged
requirement on the branch
apply method at some point? I thought I set that up before, but now I can't seem to figure out what I did before.Chastity Blackwell
06/29/2023, 6:48 PMJustin S
07/05/2023, 6:36 PMInitializing the backend...
Upgrading modules...
╷
│ Error: Unsupported Terraform Core version
│
│ on <http://backend.tf|backend.tf> line 2, in terraform:
│ 2: required_version = "= 1.3.7"
│
│ This configuration does not support Terraform version 1.5.2. To proceed,
│ either choose another supported Terraform version or update this version
│ constraint. Version constraints are normally set for good reason, so
│ updating the constraint may lead to other errors or unexpected behavior
Justin S
07/06/2023, 2:10 PMMichael Coombs
07/06/2023, 4:52 PMatlantis plan
checking if workspace exists: stat /home/atlantis/.atlantis/repos/cdd/terraform-terragrunt-vault/5/default: no such file or directory
config is github/aws/fargate - no kubernetes. I'm using a custom image of the standard atlantis docker image where i've added terragrunt. My atlantis.yaml is this:
version: 3
projects:
- name: vault-base-infra-qa
dir: env/qa/vault-base-infra
autoplan:
enabled: true
when_modified:
- '*.tf'
- '*.hcl'
- terragrunt.hcl
branch: /some-branch/
plan_requirements: [ ]
apply_requirements: [ approved ]
import_requirements: [ approved ]
workflow: terragrunt
- name: vault-base-infra-prod
dir: env/prod/vault-base-infra
autoplan:
enabled: true
when_modified:
- '*.tf'
- '*.hcl'
- terragrunt.hcl
branch: /some-branch/
plan_requirements: [ ]
apply_requirements: [ approved ]
import_requirements: [ approved ]
workflow: terragrunt
workflows:
terragrunt:
plan:
steps:
- env:
name: TERRAGRUNT_TFPATH
command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
- env:
# Reduce Terraform suggestion output
name: TF_IN_AUTOMATION
value: 'true'
- run: terragrunt plan -out $PLANFILE
apply:
steps:
- env:
name: TERRAGRUNT_TFPATH
command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
- env:
# Reduce Terraform suggestion output
name: TF_IN_AUTOMATION
value: 'true'
- run: terragrunt apply $PLANFILE
any help or guidance or would be much appreciated.Justin S
07/06/2023, 6:10 PMJustin S
07/06/2023, 6:12 PMError: Plugin did not respond
Justin S
07/06/2023, 7:15 PMJustin S
07/06/2023, 7:15 PMJustin S
07/06/2023, 7:17 PMfailed to instantiate provider
almost everywhereJustin S
07/06/2023, 7:24 PMJustin S
07/06/2023, 7:48 PMJustin S
07/06/2023, 7:51 PMJustin S
07/06/2023, 7:55 PMJustin S
07/06/2023, 7:55 PMJaycee Bernardino
07/06/2023, 9:47 PM--skip-clone-no-changes
to work? I enabled debug, have the environment set, and I am using github client which should support single file download, but it still doesn’t seem to be traversing this part of the code
It can parse my atlantis.yaml
after the clone. Could there be something else I am missing in order to get this to work?David Parreira
07/07/2023, 8:36 AMatlantis plan
and it randomly fails to plan the projects with the error
Error: Required plugins are not installed
However, individually the projects plan fine.
I've already reduced the parallel_pool_size
to 0 and to 1 but I keep having the same problem.Luiz Silva
07/10/2023, 9:06 PMRemote state S3 bucket does not exist or you don't have permissions to access it. Would you like Terragrunt to create it? (y/n)
The bucket it’s empty and I didn’t run any terraform/terragrunt commands. I’ve noticed that If I change the config to another bucket that I ran terragrunt init, it works, but my scenario is focused on empty buckets. Someone had this error?
PS: My bucket dosen’t have any policy and my role is with s3:*
Thanks in advance!Ricardo Silveira
07/11/2023, 10:53 AMRémi FLAMENT
07/12/2023, 12:23 PMatlantis apply
The service side config parameter apply_requirements: [approved]
is not evaluated.
I tried 2 ways to add my server-side config using the flag --repo-config
or --repo-config-json
This is not working, I can comment an apply, and it's done without the approval protection.
It's important to notice that I successfully set up an approval protection with the deprecated flag --require-approval
But the problem is that this flag fixed the "approved" requirements on plan
,apply
and import
. I only want to configure "approved" on apply
Open issue talking about it :
• https://github.com/runatlantis/atlantis/issues/2605 (October 22 - atlantis 0.20.1)
My env :
• Atlantis latest 0.24.3
• GitLab Enterprise 16.2.0
• Atlantis installed with the binary on EC2
• Permission for Atlantis : group access token with "developer" access
My config :
server configuration
atlantis-url: '<https://atlantis.xxxxxx.io>'
gitlab-token: 'xxxxxxxx'
gitlab-user: 'atlantis'
gitlab-webhook-secret: 'xxxxxxxx'
log-level: 'info'
repo-allowlist: '<http://gitlab.com/xxxx/yyyy/*,gitlab.com/xxxxx/zzzzz/aaaaa/*|gitlab.com/xxxx/yyyy/*,gitlab.com/xxxxx/zzzzz/aaaaa/*>'
repo-config-json: '{"repos":[{"apply_requirements":["approved"],"id":"/.*/","repo_locking":true}]}'
web-basic-auth: 'true'
web-password: 'xxxxxxxxxxxx'
web-username: 'skello'
write-git-creds: 'true'
service side config
repos:
- id: /.*/
repo_locking: true
apply_requirements: [approved]
This is probably the feature I wanted from Atlantis to allow our devs to contribute to our terraform code base in a secure way 😬
If anyone succeeds in doing this in GitLab SaaS, please help 🙏