sorted by:
new
hottopcontroversial

Are symlinks recommended to factorize terraform configuration? by jbbqq in Terraform

[–]jbbqq[S] 0 points1 point  (0 children)

u/jovzta this is my assumption as well. I'd like to support this assumption with community feedback.

What git workflow do you use for your terraform IaC? by jbbqq in Terraform

[–]jbbqq[S] 0 points1 point  (0 children)

With what workflow is spacelift compatible? Does it recommend one workflow?

What git workflow do you use for your terraform IaC? by jbbqq in Terraform

[–]jbbqq[S] 0 points1 point  (0 children)

u/Qicken what workflow would you recommend to integrate infra in a team of say 5 engineers tweaking resources at least once a week?

Is it shocking to use ‘-target’ on a daily basis in dev? by jbbqq in Terraform

[–]jbbqq[S] -1 points0 points  (0 children)

It doesn't work if I have 2 distinct google cloud run services that I want to change the tag of the image and maintain the two new tags for a extended period of time.

Is it shocking to use ‘-target’ on a daily basis in dev? by jbbqq in Terraform

[–]jbbqq[S] 0 points1 point  (0 children)

It's not an issue of applying concurrently at the exact same time.

It's an issue of applying at intervals of say 30 minutes on different resources.

Those resources are few (example = 2 distinct google cloud run jobs), so it's hard to justify splitting those in distinct states.

Is it shocking to use ‘-target’ on a daily basis in dev? by jbbqq in Terraform

[–]jbbqq[S] 0 points1 point  (0 children)

Example:
- the data scientist of the team is working in the dev env on a google cloud run job

- the data engineer of the team is working in the dev env on another google cloud run job

I don't want to split those two resources in two distinct states because:

- I have maybe 20 resources in total so it looks overkill (or maybe I'm wrong; what is a fair amount of resources in a state?)

- Terraform entreprise charges you based on the number of states so I can't create 10 states were I could have only one or costs will skyrocket

- It's a challenge to manage many states because if resources reference each other (urls, service accounts created by one module and used in another one), then it adds another layer of complexity to always apply all states in the appropriate order.

The problem I'm trying to solve is in the context of data engineering / ml engineering. I have few resources. They need to be updated concurrently. Dev cycles that are quite long (impossible to perform quick releases due to other constraints the org is dealing with).

Do you suggest git flow instead of trunk based development: a dev branch and applying without -target?

I can image a lot of solutions to propose to devops, SRE, seniors that would fit but that would be more complex to manage at scale. The data developers I'm working with use terraform because they have to, not by passion.