How to contribute

Overview

This document explains the processes and practices recommended for contributing enhancements to the Content-cache-k8s operator.

• Generally, before developing enhancements to this charm, you should consider opening an issue explaining your use case.

• If you would like to chat with us about your use-cases or proposed implementation, you can reach us at Canonical Mattermost public channel or Discourse.

• Familiarising yourself with the Charmed Operator Framework library will help you a lot when working on new features or bug fixes.

• All enhancements require review before being merged. Code review typically examines

  • code quality

  • test coverage

  • user experience for Juju operators of this charm

• Please help us out in ensuring easy to review branches by rebasing your pull request branch onto the main branch. This also avoids merge commits and creates a linear Git commit history.

Developing

The code for this charm can be downloaded as follows:

git clone https://github.com/canonical/content-cache-k8s-operator

You can use the environments created by tox for development:

tox --notest -e unit

source .tox/unit/bin/activate

Testing

Note that the content-cache-image image needs to be built and pushed to microk8s for the tests to run. It should be named localhost:32000/content-cache:latest so that Kubernetes knows to pull them from the microk8s repository. Note that the microk8s registry needs to be enabled using microk8s enable registry. More details regarding the Docker images below. The following commands can then be used to run the tests:

• tox: Runs all of the basic checks (lint, unit, static, and coverage-report).

• tox -e fmt: Runs formatting using black and isort.

• tox -e lint: Runs a range of static code analysis to check the code.

• tox -e static: Runs other checks such as bandit for security issues.

• tox -e unit: Runs the unit tests.

• tox -e integration: Runs the integration tests.

Build charm

Build the charm in this git repository using:

charmcraft pack

For the integration tests (and also to deploy the charm locally), the content-cache image is required in the microk8s registry. To enable it:

microk8s enable registry

The following commands push the required image into the registry:

docker build . -f content-cache.Dockerfile -t localhost:32000/content-cache:latest

docker push localhost:32000/content-cache:latest

Deploy

# Create a model
juju add-model content-cache-k8s-dev
# Enable DEBUG logging
juju model-config logging-config="<root>=INFO;unit=DEBUG"
# Deploy the charm (Assuming you're on amd64)
juju deploy ./content-cache-k8s_ubuntu-20.04-amd64.charm \
--resource content-cache-image=localhost:32000/content-cache:latest

Canonical contributor agreement

Canonical welcomes contributions to the Content-cache-k8s Operator. Please check out our contributor agreement if you’re interested in contributing to the solution.