github stephrobert/feint v0.7.2

latest releases: v0.16.0, v0.15.0, v0.14.0...
3 months ago

Added

  • 140 of 175 routes are proven by a real client, up from 132. The eight are
    the ones OSC-3 and OSC-4 named among their deliverables and no client had ever
    driven: the four NIC operations, ReadNatServices, and the three updates
    Terraform never walks because it replaces rather than updates — UpdateRoute,
    UpdateVolume, UpdateImage. Both batches (#10, #13) close on that, rather
    than on operations being served.

Fixed

  • An attached network interface reported a link state the Terraform provider
    refuses.
    LinkNic.State published in-use, which is the state of the
    interface; the state of the link is attached, and the provider polls
    ReadNics until it reads that. It gave up with unexpected state 'in-use', wanted target 'attached, detached, failed', leaving an apply half done and a
    destroy unable to finish. The same file rendered attached for the primary
    NIC inside a Vm four dozen lines away — one field, two spellings — and the
    unit test asserting in-use was holding the wrong one in place under a name
    claiming it matched a recording, when feint shapes records field trees and
    never values.

  • A recording could stop early and say nothing. Some APIs hand the client an
    address in a response body — Exoscale publishes an api-endpoint per zone —
    and a client that follows it walks away from the proxy for everything after.
    Measured on a real account: a session worth about ninety exchanges recorded
    eight, and the transcript looked complete. feint proxy now counts
    responses that named a host other than the one the client is addressing, names
    those hosts when the run ends, and says plainly that whatever went there is
    absent from the file.

    Detected by shape rather than by field name — an absolute URL whose host is
    not the client's — because naming api-endpoint would put one provider's
    vocabulary into a tool that carries none, and the next API to do this would be
    silent all over again. Two properties carry their own tests: an answer naming
    the proxy itself is not a handoff, because the emulator's own zone list
    points back at itself and an alarm that fires on the normal case gets ignored;
    and a gzipped body is decompressed before the scan, because scw and exo
    both send Accept-Encoding and a scan over compressed bytes finds nothing in
    a way that reads like nothing being there.

    It does not rewrite the address, deliberately: a recorder that edits what it
    records is not one. docs/proxy.md now states what a recording can promise
    for all three providers rather than for Outscale alone — one refuses loudly,
    one used to truncate quietly, one records whole (#92).

Don't miss a new feint release

NewReleases is sending notifications on new releases.