Skip to content

v2.2.1

Choose a tag to compare

@kinncj kinncj released this 13 Oct 03:31
· 40 commits to main since this release

Maple Harness v2.2.1

Highlights

  • Developer sign-in, step by step with pictures, and clearer words along the way; a sign-in revoked at the hub
    now shows at once. See
    How developers sign in.
  • CI recipes for running Maple Harness in a pipeline, and clearer advice when a run cannot verify its proxy.
  • Settings from a ConfigMap: an id given to someone else no longer keeps the previous person's sign-in.

Added

  • CI recipes for Maple Harness. CI jobs and containers
    now has copy-paste GitHub Actions and shell examples: start the proxy in the job (recommended: nothing to set, the
    harness verifies it), or connect to a proxy in a service container with maple-harness proxy connect --token-env,
    with what each guarantees, and how a script tells a run that did not start (exit status 1 and the line This session cannot ask you, so it did not start.).

Fixed

  • maple-harness serve on an unverified proxy now says why it did not start plainly, like --prompt and
    --rpc (it printed the message behind a log time stamp), and exits with status 1 as they do.
  • An unverified proxy's fixes now fit its cause. A restart is suggested only for your own proxy on an older
    release; a proxy of another identity (another user, settings folder or a container) gets sharing the settings
    folder, trust_unchecked or proxy connect; another program on the port gets "stop it, or give your proxy another
    port"; and when the harness cannot tell, each fix says which case it is for. The same in proxy status,
    maple-harness doctor and the start-up note.
  • A proxy on this machine that asks for an access token, used with trust_unchecked: a run nobody can answer
    now stops after the first refusal (exit status 1) instead of sending requests until the proxy locks it out
    ("429: too many failed attempts"), and every such refusal says to connect to it with maple-harness proxy connect --token-env, since no token is sent to a proxy that is not verified as yours.
  • Upgrading a CI job from 2.1, corrected: a job whose config.yaml names harness.proxy.token without
    harness.proxy.url (a proxy in a container that asks for a token) is not fixed by MAPLE_TRUST_UNCHECKED_PROXY=1,
    because the token is never sent to a proxy that cannot prove it is yours: run maple-harness proxy connect --token-env MAPLE_PROXY_TOKEN <address> instead. The 2.2.0 notes said either way would do.
  • Settings from a ConfigMap: an id given to someone else no longer keeps the old person's single sign-on. When
    the proxy cannot write its settings, a person without a sign_in_marker line is now told apart by the addresses
    setup_page.sso.people names them by. Remove a person and add someone else with the same id in one edit, with other
    addresses (or none): within seconds of a replica reading the file, the old account stops signing in as that id,
    what was made for the old person is cleared and the tokens they made for themselves are revoked (sso.prune,
    reason=identity_changed). Team, budget, model and account edits never end a sign-in, and neither does adding an
    address or removing one of several; a sign_in_marker line still wins. Removing all of a person's addresses now
    ends their sign-in (put the line back and they sign in again). At the first start after the upgrade, sign-ins made
    with 2.2.0 are kept when the ConfigMap still names their address for that person; one whose address it no longer
    names (an id given to someone else while 2.2.0 ran, or the line removed after the first sign-in) is cleared with its
    terminals and own tokens, and a developer whose GitHub account lists another address first may have to sign in once
    more. See
    Kubernetes.
  • Developer sign-in, clearer words and layout. With developer sign-in on, the sign-in page names the proxy and
    says admins manage it there and developers get their own access there (it spoke of the setup page to everyone). An
    account that is not allowed is told "is not allowed to sign in here. Ask an admin of this proxy to add your company
    account or domain."; one refused only when the sign-in finishes gets the same page instead of "start again". The
    Request sent page is a proper sentence. A tool whose request goes to a hub that revoked this proxy's sign-in
    is told what to do ("The hub … refused this proxy's access (the sign-in was revoked or expired). Sign in again on
    the proxy's Hubs & chaining tab, or run maple-proxy chain connect --sso …"), still as a 502, without the hub's raw
    answer, which is in the proxy's log. maple-proxy chain status lists each hub as a short block that fits an
    80-column terminal and says REVOKED: sign in again for a sign-in the hub ended (its JSON adds revoked);
    the sign-ins' heading is now Sign-ins with a company account:. The Sign in again button keeps that one label
    everywhere, the wizard's Developer sign-in choices are short with their help below, and a request on People
    & teams
    keeps Accept and Refuse together on phones and wide screens. The single sign-on wizard's
    Groups to teams box is three lines tall, as meant, instead of a tall empty box.
  • A sign-in revoked at the hub shows at once. maple-proxy chain status (every run), and the setup page, the
    hub provider's health and maple-harness doctor (at most once a minute) now ask the hub whether this proxy's
    sign-in token still works, so a revocation on My access or by an admin shows as REVOKED: sign in again right
    away, before any request. A hub that does not answer is said to have not answered, never taken for a revocation;
    a hub before 2.2.0 cannot be asked and shows it at the next request or renewal, as before.

Upgrading

  • Settings from a ConfigMap (approved security fix): removing every one of a person's addresses from
    setup_page.sso.people now ends their developer sign-in, and at the first 2.2.1 start a 2.2.0 sign-in whose address
    the map no longer names for that person is ended. Put the address line back and the person signs in again.

Known limitations

  • The new sign-in walkthrough was captured with the demo's stand-in identity provider; real providers' screens look
    different. macOS and Windows were not run for this release.

Install

curl -fsSL https://raw.githubusercontent.com/kinncj/maple-harness-dist/main/install.sh | bash
irm https://raw.githubusercontent.com/kinncj/maple-harness-dist/main/install.ps1 | iex      # Windows

Update an existing install with maple-harness update. The installers and update verify every download against SHA256SUMS
(and its signature, when the project signs releases). Third-party licences: THIRD_PARTY_NOTICES.md, or maple-harness licenses.

Free for everyone to use, commercial use included. Closed source, provided as is, without warranty — see the attached LICENSE.

macOS: these binaries are not notarised, so macOS will warn if you download them by hand. The installer and maple-harness update are unaffected.
Windows: these binaries are not Authenticode-signed, so SmartScreen may warn.