Скачать или смотреть Running PostgreSQL with SSL/TLS in CircleCI

Discover how to run PostgreSQL in CircleCI with SSL/TLS using self-signed certificates. Easy step-by-step instructions included!
---
This video is based on the question https://stackoverflow.com/q/65681706/ asked by the user 'Michal Charemza' ( https://stackoverflow.com/u/1319998/ ) and on the answer https://stackoverflow.com/a/65681707/ provided by the user 'Michal Charemza' ( https://stackoverflow.com/u/1319998/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How can I run PostgreSQL in CircleCI with SSL/TLS?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Run PostgreSQL with SSL/TLS in CircleCI

In today's development environments, securing data in transit is paramount. If you're using CircleCI to run tests that interact with a PostgreSQL database, you might want to enforce secure connections using SSL/TLS. In this guide, we'll cover a simple, effective method for running PostgreSQL with SSL/TLS in CircleCI, using a self-signed certificate.

The Challenge

You need to configure a PostgreSQL database in a CircleCI environment with SSL/TLS enabled. To achieve this without requiring additional setup, such as volumes or copying files into the container, we will utilize the CircleCI Docker executor with a default PostgreSQL image.

The Solution: Configuration Breakdown

To accomplish this, you need to modify the CircleCI configuration file, typically named .circleci/config.yml. Follow these steps to set it up correctly:

Step 1: YAML Configuration

Here’s the configuration you need to add to your .circleci/config.yml file:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Breakdown of the Configuration

Version Declaration: Start with specifying the version of your CircleCI config file structure.

Jobs Section: Create a job named build which the CircleCI will run.

Docker Images:

The first image refers to the base image where your tests will be executed. In our case, it's a python:3.8.7 image. Replace it as needed based on your project requirements.

The second image is the CircleCI PostgreSQL image, which will serve as your database.

Environment Variables: Set environment variables, like POSTGRES_PASSWORD, to ensure your PostgreSQL instance has a password for secure access.

Custom Entry Point: Override the default entry point to use bash. This allows us to execute commands before starting PostgreSQL.

Command Sequence:

First, we generate a self-signed SSL/TLS certificate using OpenSSL.

Change ownership of the generated key file to the PostgreSQL user for appropriate access.

Set the required permissions to ensure the key is secure.

Finally, the command will execute the original PostgreSQL entry point with SSL configurations enabled, specifying the generated certificate and key.

Step 3: Running Your Tests

Once the configuration is complete, you can proceed to run your tests as you normally would in CircleCI. The PostgreSQL instance should now be protected by SSL/TLS, and your connections will be secure.

Conclusion

Using CircleCI for database tests in a secure way is not only possible, but it's also straightforward. By following the steps outlined in this guide, you can successfully run your PostgreSQL database with SSL/TLS enabled, protecting your data in transit with minimal effort.

Implementing such configurations is crucial in today’s environment where security cannot be compromised. Happy coding, and may your tests run smoothly and securely!