Repository navigation
Tags
Tags
Bump osprey-rpc to 0.2.0 (#44) The sync ProcessActionRequest RPC gained the encrypted_json_secret_data field (#41), but the package version stayed at 0.1.0, so the artifact published from 1.1.1-discord.2 collides with the roostorg 0.2 release's osprey_rpc-0.1.0 despite having different contents. Bump the version so downstream pins are unambiguous.
Fix osprey-rpc release output directory (#43) ## Description - Added `--out-dir dist` option to the `osprey-rpc` build instructions I tried creating a new Osprey release, but it failed the `release-osprey-rpc` workflow with this error: ``` An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/osprey/osprey/osprey_rpc/dist'. No such file or directory ``` ## Checklist - [ ] Tests pass locally - [ ] `uv run ruff check .` passes (no unused imports or other lint errors) - [ ] `uv tool run fawltydeps --check-unused --pyenv .venv` passes (no unused dependencies) - [ ] Updated `CHANGELOG.md` with my changes, if applicable
Add `secret_data_json` field to sync `ProcessActionRequest` (#41) ## Description - Added `secret_data_json` field to `ProcessActionRequest` proto message - Updated coordinator to populate `OspreyCoordinatorAction.secret_data` using the `secret_data_json` field - Created `SecretDataDecryptor` that decrypts the secret data in the action ## Checklist - [ ] Tests pass locally - [ ] `uv run ruff check .` passes (no unused imports or other lint errors) - [ ] `uv tool run fawltydeps --check-unused --pyenv .venv` passes (no unused dependencies) - [ ] Updated `CHANGELOG.md` with my changes, if applicable