Ops (the operator framework itself)
- The current version of
opsis still 0.6.1. We had planned to release 0.7 last Thursday but have delayed it until tomorrow due to some external factors impacting our ability to wrap up needed feature work. We’ll post a quick update here when that is actually released.
- We finally got the definitive name for the project on read the docs! Feel free to bookmark, share, etc. https://ops.rtfd.io/
- We released 0.2.0, which is the first release to talk to the store (hardcoded to the staging store at the moment). Right now only three commands, all related to authentication:
logout. More will follow.
charmcraftsnap is available for testing with 0.2.0 as well. It’s strictly confined, based on
core20, and we’re looking for feedback about in which situations it fails to work as expected. It ships with an internal
charmcraft buildof charms that have
gitURLs in their
requirements.txt. It’s been tested with requirements with submodules, against projects in both launchpad and github. In some situations a submodule will cause git to try to use ssh, and that will not work. It should be possible to change the URL to something that doesn’t need to use ssh; reach out when (not if) you find issues with this (or if you can help qualify “some situations”). It does not currently ship with
hgbut those can be added. Note the internal
gitcan’t currently access the config from your home, pending a snapcraft process; you can copy
~/.config/git/config) to `~/snap/charmcraft/.
Review of charm code continues, and we’ve settled on directly filing bugs on charms and components for issues we find during review. Progress on
ops.lib.use use and documentation stalled but should continue this week.