[charm lib] Update dependency ops to v2.6.0 - autoclosed #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.4.1->2.6.0Release Notes
canonical/operator (ops)
v2.6.0: : Harness.handle_exec, Harness.add_relation improvements, and moreCompare Source
This release has two significant improvements to
testing.Harness:Harness.handle_execto allow charm tests to simulateContainer.execcalls (Pebble one-shot commands) and provide expected output. Thanks @weiiwang01 for the design and implementation (PR 993).app_dataandunit_dataparameters toHarness.add_relation. Previously, charm tests would have to calladd_relationfollowed byadd_relation_unitandupdate_relation_data-- now only a singleadd_relationcall is required. Implemented in PR 994.In addition, several small improvements and fixes are included:
Secret.unique_identifier(XID part); improve id/label docs in https://github.com/canonical/operator/pull/986push()encoding if source is a binary file or stream in https://github.com/canonical/operator/pull/991cgimodule in Pebble code in https://github.com/canonical/operator/pull/996See all changes from 2.5.0 to 2.6.0.
v2.5.1: : Fix str vs bytes issue with testing push()Compare Source
This is a patch fix on top of 2.5.0 to fix #990: "TypeError: write() argument must be str, not bytes" in
Container.pushunderHarness.v2.5.0: : Harness.get_filesystem_root, Pebble service context, and moreCompare Source
This release includes three significant additions:
collect_app_statusandcollect_unit_statusevents. This is useful for letting the framework automatically evaluate application (or unit) status from various components of the charm. We'll be documenting this properly soon, but in the meantime, read the API reference docs onCollectStatusEvent. PR #954.Harness's test filesystem from an in-memory filesystem to use a temp directory on the real filesystem; useHarness.get_filesystem_rootto get the temp filesystem directory for a specific container. This makes testing container filesystem operations significantly easier and allows tests to use the regular Python file APIs to interact with it. Thanks @weiiwang01 for his efforts on this in #960.Other notable changes:
JujuVersion.supports_open_port_on_k8sby @carlcsaposs-canonical in PR #965charmcraft.yamlin the testing harness by @syu-w in PR #977In addition, the following developers made their first contribution:
We also made several other minor improvements to type annotations and a few other tweaks. See the full changelog: canonical/operator@2.4.1...2.5.0
Configuration
📅 Schedule: Branch creation - "after 1am and before 3am every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.