0.2.2rc1

Full Changelog: 0.2.1...0.2.2rc1

0.3.0a2

Full Changelog: 0.2.1...0.3.0a2

0.3.0a1

Full Changelog: 0.2.0...0.3.0a1

0.2.1

Release Notes

• Refactored module to inherit provider configuration from root module in order to support count on the bignbit module.

Note

If bignbit was previously deployed without using count and count is added, most resources will need to be destroyed and recreated as they will transition from a single item to a list of 1 item. This will require extra care to be taken during deployment including potentially emptying both the ECR repository and the S3 staging bucket to allow for deletion. Alternatively it may be possible to terraform import the existing resources into the new plan but that was not tested.

Test Results

Tested in services UAT by setting count = 1 on the bignbit module and running terraform apply

Changelog

[0.2.1]

Added

Changed

Deprecated

Removed

Fixed

• issues/50: Fixed bug where count is unsupported for bignbit by inheriting the AWS provider config from the root module

Security

What's Changed

• Release/0.2.1 by @frankinspace in #51

Full Changelog: 0.2.0...0.2.1

0.2.1rc4

Full Changelog: 0.2.0...0.2.1rc4

0.2.1rc3

Full Changelog: 0.2.1rc2...0.2.1rc3

0.2.1rc2

Full Changelog: 0.2.1rc1...0.2.1rc2

0.2.1rc1

Full Changelog: 0.2.0...0.2.1rc1

0.2.0

Release Notes

• Two configuration options have changed names. Any existing configuration files will need to be updated to reflect these changes.
  • operaTreatment changed to operaHLSTreatment
  • convertToPNG changed to sendToHarmony.
• Input variable names changed:
  • pobit_audit_bucket -> bignbit_audit_bucket
  • pobit_audit_path -> bignbit_audit_path
• Default values for variables config_dir and bignbit_audit_path have changed as shown in the table below. This change can be ignored by explicitly setting the module input variables to the old default values.

Module Input Variable Name	Old default	New Default
config_dir	dataset-config	big-config
bignbit_audit_path	pobit-cma-output	bignbit-cnm-output

• There is a new variable bignbit_staging_bucket for the module. If not set (recommended), a new s3 bucket will be created for storing harmony results via https://harmony.earthdata.nasa.gov/docs#user-owned-buckets-for-harmony-output. Alternatively, to use an s3 bucket that already exists, set the variable bignbit_staging_bucket to the name of the bucket to be used. Be sure the bucket policy permissions are set correctly to allow Harmony write and GIBS read permission to this bucket.
• lambda_role variable has been removed and instead replaced by permissions_boundary_arn, this will need to be updated in the cumulus deployment terraform for the bignbit module.
• The prevent_destroy flag for gibs_response_topic has been turned on to help avoid accidental deletion of the topic used for responses from GIBS
• Terraform v1.5.3 should be used for deployment

What's Changed

• feature: convertToPNG --> sendToHarmony by @voxparcxls in #21
• Update README.md by @frankinspace in #22
• Issue#16: Change apply opera treatment choice and lambda to be specific to HLS by @voxparcxls in #24
• Feature/issue 7 - Remove wait for GITC response by @torimcd in #30
• Support datetimes without microseconds by @jtherrmann in #37
• Update generate_image_metadata.py by @frankinspace in #39
• Issues/23: Enable Harmony write output to user bucket by @frankinspace in #46
• Add new message attribute response_topic_arn by @frankinspace in #47
• Release/0.2.0 by @frankinspace in #49

New Contributors

• @jtherrmann made their first contribution in #37

Full Changelog: 0.1.2...0.2.0
Test Results: #49

0.2.0rc11

Full Changelog: 0.2.0rc10...0.2.0rc11