terraform-provider-argocd
terraform-provider-google
| terraform-provider-argocd | terraform-provider-google | |
|---|---|---|
| 2 | 16 | |
| 361 | 2,224 | |
| 1.1% | 0.8% | |
| 7.3 | 9.9 | |
| 8 days ago | 3 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-argocd
-
Is using an argocd provider for terraform an anti-pattern? Why not just use helm provider?
I'm looking at projects like https://github.com/oboukili/terraform-provider-argocd and wondering if using this project would be an anti-pattern? For context I have a repo hosted with DigitalOcean that looks like atlantis provisioning terraform code folder -> atlantis code -> argocd -> pritunl. I'm thinking I want my initial terraform code to provision atlantis, then have atlantis provision an argocd server, then have argocd provision a custom pritunl helm chart. Just wondering if I should use Terraform to manage the argocd provisioning aspect of it or not and if it makes sense?
-
How to allow dynamic Terraform Provider Configuration
I'll use the example of the Argo CD provider. In a single Terraform run, we would like to:
terraform-provider-google
-
OpenBSD System-Call Pinning
> DNS without CGO works perfectly
It does not. I know this because it impacts my daily work and the work of others. Honestly if you could make my day and go figure out exactly what's going wrong with the pure go DNS implementation it would make my life alot simpler and I wouldn't have to maintain shell scripts that update etc/hosts to hard code in ipv4 addresses for the APIs I access with terraform.
https://github.com/hashicorp/terraform-provider-google/issue...
-
Exploring GCP With Terraform: Setting Up The Environment And Project
GCP Terraform Provider
-
Is there a provider like AzApi for GCP and AWS?
I think the equivalent for AWS is https://registry.terraform.io/providers/hashicorp/aws/latest/docs and for GCP https://registry.terraform.io/providers/hashicorp/google/latest/docs
- How do you reference the underlying Cloud Run instance in Cloud Functions V2?
-
When will Terraform include support for GCP Datastream service ? It has been 1 year since its public release
There's an open issue in the gcp provider for exactly this. I'd recommend thumbs-upping it if you haven't already, as well as subscribing to notifications so you can see when there are updates.
-
Is Google Cloud DataPlex available to use from Terraform?
only some people inside google could answer that but here's an issue already? https://github.com/hashicorp/terraform-provider-google/issues/11648
- Coding through the war / Looking for a volunteer project
-
error with auth and login
Not sure if you've solved for this or not, but it didn't work for me running terraform as a service account, it appears that it doesn't handle HTTP headers correctly: https://github.com/hashicorp/terraform-provider-google/issues/6738 but it does work with impersonation of that account, which is what I did. Note that your org can only have 1 access policy, and in my case I had to make google_access_context_manager_access_level anyways.
-
Google Maps (Geocode) and Terraform - Possible to provision an API key?
All I can find is an old thread saying cannot do. https://github.com/hashicorp/terraform-provider-google/issues/6413 Has there been any update to this, or does anyone know of a work around?
-
TF impersonate code
If you followed that request, you get to this PR which added the feature and updated this documentation
What are some alternatives?
terraform-kubernetes-manifests - Terraform modules for managing Kubernetes manifests
terraform-provider-netlify - Terraform Netlify provider. Please note: This Terraform provider is archived per our provider archiving process: https://terraform.io/docs/internals/archiving.html
devops-stack - 🌊 An all-in-one Kubernetes ☸ stack using Argo CD 🐙 and Terraform as base components
terraform-provider-grafana - Terraform Grafana provider
terraform-provider-aws - Terraform AWS provider [Moved to: https://github.com/hashicorp/terraform-provider-aws]
terraform-provider-rancher2 - Terraform Rancher2 provider
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
terraform-provider-solana - Data source provider for Terraform that interacts with the Solana networks
terraform-provider-unifi - Terraform provider for Unifi :satellite:
helmfile - Deploy Kubernetes Helm Charts
terraform-example-foundation - Shows how the CFT modules can be composed to build a secure cloud foundation
Fail2Ban - Daemon to ban hosts that cause multiple authentication errors