Skip to content

Cassandra

Since testcontainers-go v0.26.0

Introduction

The Testcontainers module for Cassandra.

Adding this module to your project dependencies

Please run the following command to add the Cassandra module to your Go dependencies:

go get github.com/testcontainers/testcontainers-go/modules/cassandra

Usage example

ctx := context.Background()

cassandraContainer, err := cassandra.RunContainer(ctx,
    testcontainers.WithImage("cassandra:4.1.3"),
    cassandra.WithInitScripts(filepath.Join("testdata", "init.cql")),
    cassandra.WithConfigFile(filepath.Join("testdata", "config.yaml")),
)
if err != nil {
    panic(err)
}

// Clean up the container
defer func() {
    if err := cassandraContainer.Terminate(ctx); err != nil {
        panic(err)
    }
}()

Module reference

The Cassandra module exposes one entrypoint function to create the Cassandra container, and this function receives two parameters:

func RunContainer(ctx context.Context, opts ...testcontainers.ContainerCustomizer) (*CassandraContainer, error)
  • context.Context, the Go context.
  • testcontainers.ContainerCustomizer, a variadic argument for passing options.

Container Options

When starting the Cassandra container, you can pass options in a variadic way to configure it.

Image

If you need to set a different Cassandra Docker image, you can use testcontainers.WithImage with a valid Docker image for Cassandra. E.g. testcontainers.WithImage("cassandra:4.1.3").

Image Substitutions

In more locked down / secured environments, it can be problematic to pull images from Docker Hub and run them without additional precautions.

An image name substitutor converts a Docker image name, as may be specified in code, to an alternative name. This is intended to provide a way to override image names, for example to enforce pulling of images from a private registry.

Testcontainers for Go exposes an interface to perform this operations: ImageSubstitutor, and a No-operation implementation to be used as reference for custom implementations:

// ImageSubstitutor represents a way to substitute container image names
type ImageSubstitutor interface {
    // Description returns the name of the type and a short description of how it modifies the image.
    // Useful to be printed in logs
    Description() string
    Substitute(image string) (string, error)
}

type NoopImageSubstitutor struct{}

// Description returns a description of what is expected from this Substitutor,
// which is used in logs.
func (s NoopImageSubstitutor) Description() string {
    return "NoopImageSubstitutor (noop)"
}

// Substitute returns the original image, without any change
func (s NoopImageSubstitutor) Substitute(image string) (string, error) {
    return image, nil
}

Using the WithImageSubstitutors options, you could define your own substitutions to the container images. E.g. adding a prefix to the images so that they can be pulled from a Docker registry other than Docker Hub. This is the usual mechanism for using Docker image proxies, caches, etc.

Wait Strategies

If you need to set a different wait strategy for the container, you can use testcontainers.WithWaitStrategy with a valid wait strategy.

Info

The default deadline for the wait strategy is 60 seconds.

At the same time, it's possible to set a wait strategy and a custom deadline with testcontainers.WithWaitStrategyAndDeadline.

Startup Commands

Testcontainers exposes the WithStartupCommand(e ...Executable) option to run arbitrary commands in the container right after it's started.

Info

To better understand how this feature works, please read the Create containers: Lifecycle Hooks documentation.

It also exports an Executable interface, defining one single method: AsCommand(), which returns a slice of strings to represent the command and positional arguments to be executed in the container.

You could use this feature to run a custom script, or to run a command that is not supported by the module right after the container is started.

Docker type modifiers

If you need an advanced configuration for the container, you can leverage the following Docker type modifiers:

  • testcontainers.WithConfigModifier
  • testcontainers.WithHostConfigModifier
  • testcontainers.WithEndpointSettingsModifier

Please read the Create containers: Advanced Settings documentation for more information.

Init Scripts

If you would like to do additional initialization in the Cassandra container, add one or more *.cql or *.sh scripts to the container request with the WithInitScripts function. Those files will be copied after the container is created but before it's started under root directory.

An example of a *.sh script that creates a keyspace and table is shown below:

#!/bin/bash
set -e

cqlsh -e "CREATE KEYSPACE IF NOT EXISTS init_sh_keyspace WITH REPLICATION = {'class': 'SimpleStrategy', 'replication_factor': 1};" && \
cqlsh -e "CREATE TABLE IF NOT EXISTS init_sh_keyspace.test_table (id bigint,name text,primary key (id));" && \
cqlsh -e "INSERT INTO init_sh_keyspace.test_table (id, name) VALUES (1, 'NAME');"

Database configuration

In the case you have a custom config file for Cassandra, it's possible to copy that file into the container before it's started, using the WithConfigFile(cfgPath string) function.

Warning

You should provide a valid Cassandra configuration file, otherwise the container will fail to start.

Container Methods

The Cassandra container exposes the following methods:

ConnectionHost

This method returns the host and port of the Cassandra container, using the default, 9042/tcp port. E.g. localhost:9042

connectionHost, err := container.ConnectionHost(ctx)