Even with the advent of cloud computing and all manner of technology enhancements, exposing secrets seems to be a problem that won’t go away.
Without the right controls in place, developers can leak secrets that can cause financial and reputational damage to an organisation.
In part 2, we’ll look at how we can use a pre-commit hook to try and detect secrets in our code.
Having standards for code development is a necessity but making sure those standards are followed can be a challenge.
As human beings, we make mistakes and can overlook standards at the very moment we need to apply them.
Central to that challenge is making sure standards are applied before changes are committed.
In this series, we’ll look at taking on that challenge with pre-commit hooks. We’ll explore what pre-commit hooks are, why we might want to use them and how they work.
Over the years working on data platforms, I have seen architects writing less and less code, to the point where in more recent times, a seemingly growing number of architects (in data projects) are writing no code at all.