Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Don't attempt to trim keys for presets #17

Merged
merged 3 commits into from
Mar 21, 2024
Merged

Conversation

amrc-benmorrow
Copy link
Contributor

The operator was attempting to run trim_keys on Preset keys. This was failing because the Secrets were not writable by the operator.

The root cause was a bug introduced during refactoring of the account creation code.

Also forbid optional.py v2.0, newly uploaded on 13 March and with a different and useless API.

At some point this code was doing both key and account creation, and
returning a combined status object. But the refactoring was incomplete
and has led to HAS_OLD_KEYS being set in error.

As the account creation is now handled entirely separately just put this
back to what was there originally.
The API has been completely reworked and is no longer either
Java-compatible or a monad.
@amrc-benmorrow amrc-benmorrow linked an issue Mar 21, 2024 that may be closed by this pull request
@amrc-benmorrow amrc-benmorrow merged commit 9f3bd05 into main Mar 21, 2024
@amrc-benmorrow amrc-benmorrow deleted the fix/bm-presets branch March 21, 2024 11:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Preset keys fail in trim_keys
1 participant