Skip to content

Latest commit

 

History

History
62 lines (47 loc) · 2.06 KB

CONTRIBUTING.md

File metadata and controls

62 lines (47 loc) · 2.06 KB
Raw

Contributing

Overview

This documents explains the processes and practices recommended for contributing enhancements to the OSM VCA Integrator charm.

  • 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 administrators 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

You can use the environments created by tox for development:

tox --notest -e unit
source .tox/unit/bin/activate

Testing

tox -e fmt           # update your code according to linting rules
tox -e lint          # code style
tox -e unit          # unit tests
tox -e integration   # integration tests
tox                  # runs 'lint' and 'unit' environments

Build charm

Build the charm in this git repository using:

charmcraft pack

Deploy

# Create a model
juju add-model test-osm-vca-integrator
# Enable DEBUG logging
juju model-config logging-config="<root>=INFO;unit=DEBUG"
# Deploy the charm
juju deploy ./osm-vca-integrator_ubuntu-20.04-amd64.charm

Canonical Contributor Agreement

Canonical welcomes contributions to the OSM VCA Integrator Operator. Please check out our contributor agreement if you're interested in contributing to the solution.