terraform-provider-azuredevops VS nutter

Yes i agree terraform is much better.. unless one runs out of luck due to new features on azure.. https://github.com/microsoft/terraform-provider-azuredevops/labels/new-feature The cli and powershell are updated by ms much faster... but for most cases terraform is just about ok

As far as I know, there is no built-in CredScan policy in Azure DevOps. The link you shared is Azure DevOps provider in Terraform. If you get any problems to set this policy, you could go to https://github.com/microsoft/terraform-provider-azuredevops/issues to create a new issue.

Goal: I'm trying to write a new terraform provider for AzureDevops. The goal is to call pipeline (API) https://github.com/microsoft/terraform-provider-azuredevops. I forked it to my own github account. After read the code, I notice the api it used in this provider is from https://github.com/microsoft/azure-devops-go-api/tree/dev/azuredevops/pipelines. And there is a pipelines go func I need.

From my experience OO gives you much more flexibility in designing your pipeline but you're risking to make the project way more complicated. The worst example I have seen is the Nutter library (https://github.com/microsoft/nutter), which uses endless classes that are all nested in each other. I once had a bug when using it, and it was a huge pain in the ass to understand what's going on when the code is executed. It is a very good example of what can go wrong when you're overusing OO. However, in one project, I carefully created few classes, just out of curiosity, and I was very impressed how it helped me to organize/structure my code. A functions hase a clear dedicated use, but a good class is like a Swiss army knife with an solid set of functionalities. If you know how to use it in a smart way, you are likely to increase the quality of your code, but the contrary is also very likely, especially when the team members are not ready for it.

- https://github.com/microsoft/nutter