|
Docjowles posted:I'm trying to script against the Azure APIs for the first time, starting out with Python since that's my go to. Why are you going against the api and not using bicep or terraform?
|
#
¿
Jun 1, 2023 01:04
|
|
|
|
| # ¿ May 15, 2024 05:16 |
|
|
Docjowles posted:I don’t know what bicep is. Is there a terraform resource for “run an arbitrary billing query on demand”? Just checking that you're using the right tool for the job. API is probably correct.
|
|
#
¿
Jun 1, 2023 02:13
|
|
|
The Iron Rose posted:What systems do people use for automated semantic versioning of repositories? This is a general thing - it can include everything from docker images, to terraform modules, to CI/CD templates, to the actual codebases for our services (mostly python within my SRE/devops group, JS/Python/Golang for the rest of our org). I just use gitversion. It's fine, it gets the job done and doesn't require any hand holding once you get it set up which takes like 15 minutes.
|
|
#
¿
Aug 1, 2023 03:10
|
|
|
What's the pattern for handling provider versioning within Terraform modules? Let's say I have module A that is consumed by base. base says it needs provider version ~> 3.0. A says it needs provider version >= 3.0.0. They both have lock files that point to the same version, 3.5. I upgrade base from 3.5 to 3.8. base immediately breaks because Module A is on 3.5. base can't simultaneously use 3.5 and 3.8. Is the trick to simply exclude lock files from version control for modules? That seems very wrong. [edit] let's say that module A is being sourced out of a Git repo reference to a tag, not anything fancy like Terraform cloud.
|
|
#
¿
Jan 25, 2024 23:23
|
|
|
Vulture Culture posted:I believe the lock files for everything except the root module are irrelevant and are ignored, and only the constraints are considered when evaluating provider versions against modules That's not the behavior I'm encountering, although it would make sense. I'll come up with a coherent example later.
|
|
#
¿
Jan 26, 2024 00:02
|
|
|
The Fool posted:Even if lock files are parsed outside of the root module, you shouldn't use them anywhere else. So lock files should only be in root modules? Then how do you handle root module -> something that was originally also a root module but now is being used as part of a larger initiative but is also still a root module in some cases -> true, non-root module? [edit] For what it's worth, I'm trying to reign in people who are attempting to over-module things but I'm not having a ton of success. New Yorp New Yorp fucked around with this message at 00:15 on Jan 26, 2024 |
|
#
¿
Jan 26, 2024 00:12
|
|
|
|
| # ¿ May 15, 2024 05:16 |
|
|
The Fool posted:you don't Agreed and thanks for the advice. I'm desperately trying to convince people that making a separate opinionated module for every single resource is a god-awful idea but I'm not getting any traction.
|
|
#
¿
Jan 26, 2024 01:07
|
|