When building CI/CD pipelines, I follow a fundamental principle: the pipeline configuration (YAML/JSON) should be a thin orchestration layer that primarily calls scripts, while the actual logic lives in version-controlled, testable scripts.
This approach treats pipeline configuration files as mere schedulers and environment providers, not as the primary home for build logic.
Obay’s Terraform Naming Convention (OTN) is a standardized approach to organizing Terraform files that promotes clarity, consistency, and maintainability in infrastructure-as-code projects. The core principle is simple: one block per file, named according to the block type and identifier.
Full official documentation is on https://learn.hashicorp.com/vault/operations/ops-deployment-guide
1. Install Vault # Run the following commands on a freshly installed Debian Stretch
sudo apt-get update && sudo apt-get install -y unzip libcap2-bin curl VAULT_VERSION="1.4.2" curl --silent --remote-name https://releases.hashicorp.com/vault/${VAULT_VERSION}/vault_${VAULT_VERSION}_linux_amd64.zip curl --silent --remote-name https://releases.hashicorp.com/vault/${VAULT_VERSION}/vault_${VAULT_VERSION}_SHA256SUMS curl --silent --remote-name https://releases.hashicorp.com/vault/${VAULT_VERSION}/vault_${VAULT_VERSION}_SHA256SUMS.sig unzip vault_${VAULT_VERSION}_linux_amd64.zip sudo chown root:root vault sudo mv vault /usr/local/bin/ 2. Make sure the setup is working # vault --version you should see the following output:
