# Changing databases without ever accessing them

Cloud galaxy · Cédric Merlin, CTO · https://merlin-cedric.fr/en/cloud/scripts-db/

Running scripts on test and production databases with no direct access: temporary container, approval, traced result.

## The problem

Developers sometimes need to run scripts on test and production databases, without having direct access to those databases.

## What I did

1. **The script goes into Git.** The developer pushes the script to a shared code repository.
2. **A temporary container.** An automation pipeline starts a temporary container, placed in the right network.
3. **A badge for production.** For production, a team must approve first.
4. **Traced separately.** The result goes to the monitoring tool, not to the deployment pipeline logs.

## The result

No standing access to the databases to run a script. Everything is traced.

Figure: 0 standing access to the databases to run a script.

## Stack

Automation, Temporary containers, Federated identity, Databases, Monitoring

---
Page: https://merlin-cedric.fr/en/cloud/scripts-db/ · Contact: contact@merlin-cedric.fr