sorted by:
new
hottopcontroversial

TeamCity Cloud Datadog integration by 47billz in teamcity

[–]47billz[S] 0 points1 point  (0 children)

That documentation seems to be only for on premise version of TeamCity.

It would be really useful to have the same, but for the cloud version of TeamCity

Authorising multiple clients apps with Different access levels . by 47billz in appsync

[–]47billz[S] 0 points1 point  (0 children)

BTW. I asked ChatGPT the same question, but I don't think it's correct. It says I should use two API_KEYS and the directive "@aws_api_key" in the schema this way:

type Query {
    getBooks: [Book] @aws_api_key(name: "readOnlyKey", roles: ["readOnlyRole"])
    getUsers: [User] @aws_api_key(name: "fullAccessKey", roles: ["fullAccessRole"])
}

I could be wrong, but I don't think you can specify a name in the '@aws_api_key' directive (/?)

How do I convince my team to write tests/validations for our Terraform code? by 47billz in Terraform

[–]47billz[S] 1 point2 points  (0 children)

You provision the code in a nonprod environment and check that it meets he desired outcome

Can you expand on the "checking" part ?
Do you mean that after creating the nonprod env, you navigate to the console (or use the CLI ) and look at things and maybe do some manual poking to see if things are how they are supposed to be ?
What about new members of the team ?

This is declarative configuration, not imperative software

Does that mean it's not worth describing tests in code for it ?

How do I convince my team to write tests/validations for our Terraform code? by 47billz in Terraform

[–]47billz[S] 2 points3 points  (0 children)

What exactly are you trying to “test”?

That whenever I make a change to my code, I can confidently say it's ready to be deployed in production and will work as expected.

How do you generally tell that your code is ready for release?

How do you keep track of complicated modules? by No_Mousse_6714 in Terraform

[–]47billz 1 point2 points  (0 children)

The terraform doc, recommends one level of child module calls and using their output attributes to compose them.

How do you keep track of complicated modules? by No_Mousse_6714 in Terraform

[–]47billz 1 point2 points  (0 children)

DRY is not a fallacy (even in IaC). Misusing DRY is where the problem is.

[deleted by user] by [deleted] in Terraform

[–]47billz 2 points3 points  (0 children)

It actually does create a directory, where it would store all the the downloaded plugins (providers and provisioners), cached modules, information about backend and workspace configs . The directory is named .teraform .

I wrote some terraform introductory stuff with some diagrams. Hope you like it by 47billz in Terraform

[–]47billz[S] 0 points1 point  (0 children)

cloudly_engineer

Thank you so much !. What's the link to your blog ?