0.3.0a5

What's Changed

• Fixed bug causing GIBS responses to fail processing in OPS by @frankinspace in #61

Full Changelog: 0.3.0a4...0.3.0a5

0.3.0a4

Full Changelog: 0.2.3...0.3.0a4

0.2.3

Release Notes

• Following triage with the Harmony team it was discovered that bignbit should throttle requests to the Harmony API. This can be controlled via the background queue throttle for bignbit. This limits how many browse image workflows can run concurrently and should be set to no more than 100 for this release.
• A new environment variable HARMONY_SHOULD_VALIDATE_AUTH controls whether or not Harmony clients used by the lambdas will validate EDL credentials on initialization.
• This release also fixes a bug that was causing the workflow execution status in the Cumulus Dashboard to get stuck in "Running" status.

Test Results

Tested in services UAT and observed cumulus_meta is now present in the output CMA message from the step function execution. This should allow proper updating to the cumulus dashboard status but will need to be verified once installed in a cumulus environment.

Was able to successfully run 100 parallel executions in services UAT environment.

Changelog

[0.2.3]

Added

Changed

• issues/55: Harmony client changed from per request and instead will be cached as global variable and will not validate auth credentials on initialization.

Deprecated

Removed

Fixed

• issues/54: Fixed bug where status was not being reported to Cumulus Dashboard by adding cumulus_meta back into the output CMA.

Security

What's Changed

• Issues/54: Handle cumulus_meta properly by @frankinspace in #57
• Issues/55 Cache harmony client and don't validate EDL on init by @frankinspace in #56
• Release/0.2.3 by @frankinspace in #58

Full Changelog: 0.2.2...0.2.3

0.2.3rc5

Full Changelog: 0.2.3rc4...0.2.3rc5

0.2.3rc4

Full Changelog: 0.2.3rc3...0.2.3rc4

0.2.3rc3

What's Changed

• Issues/55 Cache harmony client and don't validate EDL on init by @frankinspace in #56

Full Changelog: 0.2.3rc2...0.2.3rc3

0.2.3rc2

What's Changed

• Issues/54: Handle cumulus_meta properly by @frankinspace in #57

Full Changelog: 0.2.3rc1...0.2.3rc2

0.2.3rc1

Full Changelog: 0.2.2...0.2.3rc1

0.3.0a3

Full Changelog: 0.2.2...0.3.0a3

0.2.2

Release Notes

• hashicorp/null provider is now required to meet ~>2.1

Test Results

Tested using terraform init to successfully solve provider versioning

Changelog

[0.2.2]

Added

Changed

• Lowered required version of hashicorp/null to ~> 2.1 to be compatible with the requirements of cumulus core

Deprecated

Removed

Fixed

Security

What's Changed

• Release/0.2.2 by @frankinspace in #52

Full Changelog: 0.2.1...0.2.2