Closed ingvarch closed 1 year ago
@ingvarch @mdanidl Seems like there was on update to Go 1.17. Is there still an issue with building on M1?
Sorry for delay. Yeah. It works fine.
Initializing the backend...
Initializing provider plugins...
- Finding latest version of splunk/splunk...
- Installing splunk/splunk v1.4.17...
- Installed splunk/splunk v1.4.17 (signed by a HashiCorp partner, key ID C9E90EA7C7CA45BD)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.