2.13.0 Testing User Secrets with Harness and Other Improvements

The main feature this release is the ability to work with user secrets (secrets that a Juju admin adds to the model) in Harness. You'll want to start with the new add_user_secret() method and from there can mostly manage them in the same way as application secrets.

Note that one of the fixes corrects the type of config values, which were previously strongly typed as str, when they may be int, float, bool, or str. This may break your existing type checks, although we have endeavoured to reach out preemptively with PRs to address this where possible.

Features

• Add support for user secrets in Harness in #1176
• Add pebble.CheckInfo.change_id field in #1197

Fixes

• Correct the model config types in #1183
• In Harness, only inspect the source file if it will be used - this fixes using Harness in a Python REPL in #1181

Documentation

• Update publishing a release in HACKING.md in #1173
• Add tox -e docs-deps to compile requirements.txt in #1172
• Update doc to note deprecated functionality in #1178

Tests

• First stage of converting tests from unittest to pytest in #1191, #1192, #1196, #1193, and #1195

Full Changelog: 2.12.0...2.13.0