Skip to content

Releases: moonstream-to/waggle

Waggle v0.1.4 Multiple password types support

Choose a tag to compare

@github-actions github-actions released this 20 Sep 10:00
5a0b0ef

The waggle server supports configuration with next password types:

  • plaintext
  • text_file
  • aws_secret

`waggle` v0.1.3: Improved logic when registering drops

Choose a tag to compare

@zomglings zomglings released this 16 Sep 08:38
6e7c07d

This release includes more resilient execution of waggle moonstream drop. A failure to submit a single batch (after retries) doesn't result in the process exiting. Instead, an attempt is made to register subsequent batches even if a single batch fails.

This is useful because often batches fail to submit because of duplication of request IDs. Being able to run the waggle moonstream drop command idempotently with the same input file means that such duplication is not catastrophic.

What's Changed

  • waggle moonstream drop is now idempotent on a per infile basis by @zomglings in #18

Full Changelog: v0.1.2...v0.1.3

Waggle v0.1.2

Choose a tag to compare

@github-actions github-actions released this 08 Sep 06:30
6da8043

This release fixes a the way waggle version is calculated in v0.1.1.

Now, the waggle version is specified in version.go. This release removes version.txt.

Waggle v0.1.1

Choose a tag to compare

@github-actions github-actions released this 24 Aug 18:18
f65757d

Waggle with API Server Extension.

Waggle v0.0.9

Choose a tag to compare

@github-actions github-actions released this 19 Aug 03:39

This release was created by our new automated release action: https://github.com/moonstream-to/waggle/actions/runs/5909243181

It contains waggle builds for common (OS, CPU architecture) pairs. Download the version appropriate for your environment and unzip the file to start using waggle.

Support for `request_id` in call requests

Choose a tag to compare

@zomglings zomglings released this 10 Aug 16:06
fcfca9b

This release updates waggle to support the new request_id parameter on the /metatx/call_requests endpoints. The API uses request_id to deduplicate call requests. It is the client's responsibility to generate request_ids.