I believe that achieving perfection in naming things is an elusive goal. This is not only because individuals often associate their own unique meanings with words, but also because a chosen name may inadvertently carry offensive connotations in different languages.

(in my opinion) Tofu is much better than the other alternative they suggested like Archo or EchoSphere.

Disclaimer - I also do some work with Env0 which is part of the OpenT(o)F(u) initiative

TL;DR

Running schema validation tests is important, and the sooner the better.

If all machines (local developers environment, CI, etc.) have access to your Kubernetes cluster, run `kubectl --dry-run` in server mode on every code change. If this isn’t possible, and you want to perform schema validation tests offline, use kubeconform together with a policy enforcement tool to have optimal validation coverage.

Micro-services on serverless architecture with NodeJS, GoLang, React and a little bit Python

We do support Terraform, CloudFormation and ARM Templates because those are all structured files. Unlike your source control, we are doing heavy compute processing every time a new PR created, so our costs are higher...

you will need to glue together (and maintain) a bunch of different open-source projects to achieve the same capabilities - here are some: https://github.com/danger/danger-js, https://github.com/probot/probot, https://github.com/Yelp/detect-secrets, https://github.com/github/licensed, and many more...

Yes, we plan to add GitLab and BitBucket support in the next quarter.

the git hook is only the integeration part. the core of the system is the rules engine and the logic around that.

just to clarify, Datree runs automatic checks for each custom rule that a user creates

We have a Java + Mongo stack and recently we had an issue in prod where code was deployed with a @Indexed annotation. When deployed this will create an index on startup and can lock up the DB. We had this issue years ago, but it slipped pass code review and we had a 10 minute downtime because of this. Can this be prevented using custom rules in Datree?

I believe we can provide more value than what can be achieved with a few shell scripts, for example, the built-in best practices, the rules management option, and more ;) A volume-based discount is also available for enterprise customers. If you would like to hear more - feel free to reach out to Eyar [AT] Datree IO

you are right but blocking secretes is only a subset of what our engine can do. also, as far as I know, the secret blocking feature github is offering is ONLY for public repos.