Novops makes it easier to access secrets

[sakib60]

I won't tell you anything new by saying that secrets management is important, but complicated to implement. novopspresents itself as an innovative tool that will make this task easier for you. It works just as well in your development environment as in CI/CD pipeline tools.

Use cases
You have an Infrastructure as Code project, such as india car owner data Terraform , Ansible or Pulumi , managing multiple environments (dev, preprod…). The code is executed either locally or in CI/CD pipelines, such as GitLab CI CD , GitHub Actions or Jenkins

Secrets are stored in a secret manager such as Hashicorp Vault, AWS Secret Manager, AWS STS, AWS SSM, Azure Keys Vault, GCLOUD Secret manager or Bitwarden.

How Novops works
Novops Secrets Management

Novops loads secrets into memory, mainly as environment variables, but also as files. Novops can generate files in some situations - but they are written to a filesystem tmpfs(in-memory filesystem) and thus not to disk! Additionally, Novops uses a secure directory that only the executing user novopscan access ( XDG_RUNTIME_DIR or a secure directory in /tmp ).

Installing the Novops CLI
In a terminal window, type the following commands:

Terminal window
oice. The list of releases ↗ .

Creating the novops configuration file
Trick

Before testing Novops, if you don't have a Vault accessible, you can follow this documentation to launch a test instance.

You must then, in the folder where your project requiring access to secrets is located, create a configuration file named .novops.yml, here is an example of the content.