I totally agree with keeping the code as simple and readable as possible. In my experience, classic developers tend to write less readable code due to their habit to write dry code with other languages. Your video is a good starting point for a discussion between dev and ops in a devops team, where generally there are more dev than ops.
My comment may have been deleted, so I'll repost. I don't think you're right about the .terraform.lock.hcl file. This should definitely be included into source control. The `.terraform` folder itself should be ignored. Here is the relevant blurb from terraform documentation: "Terraform automatically creates or updates the dependency lock file each time you run the terraform init command. You should include this file in your version control repository so that you can discuss potential changes to your external dependencies via code review, just as you would discuss potential changes to your configuration itself."
Interesting. Thanks for sharing! I’ve never included it in source. Never observed any malfeasance. I wonder what the impact is of including it. It seemed (in my head) as a file used by the local operator that would be unique to their local environment, also a file that gets dynamically generated when needed anyway. Do you have the link to the docs where you found this? I’d like to take a closer look! Thanks again for bringing this to my attention! 😊
@azure-terraformer I tried to link it before which is why I think my comment was deleted. If you've ever done node development this is something similar. You want every run of tf init to be locked to the same versions that you tested with. This essentially makes it so that you have a predictable deployment of all of your dependences. I'll post another comment with the link and see if it gets deleted by yt
@@azure-terraformer yeah it got deleted but if you search for terraform lock file and go to the link, the part I pasted is under "lock file location" or something like that
I totally agree with keeping the code as simple and readable as possible. In my experience, classic developers tend to write less readable code due to their habit to write dry code with other languages. Your video is a good starting point for a discussion between dev and ops in a devops team, where generally there are more dev than ops.
Glad you found it helpful! 🤗
Thank you for your content!
Glad that you enjoy it!!! ✊🤓
Please provide the URL of the PR.
Hey sorry these code ninja reviews are private!
My comment may have been deleted, so I'll repost.
I don't think you're right about the .terraform.lock.hcl file. This should definitely be included into source control. The `.terraform` folder itself should be ignored.
Here is the relevant blurb from terraform documentation:
"Terraform automatically creates or updates the dependency lock file each time you run the terraform init command. You should include this file in your version control repository so that you can discuss potential changes to your external dependencies via code review, just as you would discuss potential changes to your configuration itself."
Interesting. Thanks for sharing! I’ve never included it in source. Never observed any malfeasance. I wonder what the impact is of including it. It seemed (in my head) as a file used by the local operator that would be unique to their local environment, also a file that gets dynamically generated when needed anyway. Do you have the link to the docs where you found this? I’d like to take a closer look! Thanks again for bringing this to my attention! 😊
@azure-terraformer I tried to link it before which is why I think my comment was deleted. If you've ever done node development this is something similar. You want every run of tf init to be locked to the same versions that you tested with. This essentially makes it so that you have a predictable deployment of all of your dependences.
I'll post another comment with the link and see if it gets deleted by yt
Rgr rgr
@@azure-terraformer yeah it got deleted but if you search for terraform lock file and go to the link, the part I pasted is under "lock file location" or something like that
@decius596 are you in discord?