Skip to content

v17.0.0
Compare
Choose a tag to compare
@npauzenga npauzenga released this 13 Aug 00:55
· 103 commits to master since this release
v17.0.0
a5acb59

Release 17.0.0

Notable Changes

  • CUMULUS-3258
    • @cumulus/api is now compatible only with Orca >= 8.1.0. Prior versions of
      Orca are not compatible with Cumulus 17+
    • Updated all hashicorp terraform AWS provider configs to ~> 5.0
      • Upstream/downstream terraform modules will need to utilize an AWS provider
        that matches this range

MIGRATION notes

  • This release updates the hashicorp/aws provider required by Cumulus to ~> 5.0
    which in turn requires updates to all modules deployed with Core in the same stack
    to use a compatible provider version.
  • This update is not compatible with prior stack states - Terraform will not
    allow redeployment of a prior version of Cumulus using an older version of
    the provider. Please be sure to validate the install changeset is what you
    expect prior to upgrading to this version.
  • Upgrading Cumulus to v17 from prior versions should only require the usual
    terraform init/apply steps. As always be sure to inspect the terraform plan or
    terraform apply changeset to ensure the changes between providers are what
    you're expecting for all modules you've chosen to deploy with Cumulus

Breaking Changes

  • CUMULUS-3258

    • Update @cumulus/api/lib/orca/getOrcaRecoveryStatusByGranuleCollection
      to @cumulus/api/lib/orca/getOrcaRecoveryStatusByGranuleIdAndCollection and
      add collectionId to arguments to support Orca v8+ required use of
      collectionId

    • Updated all terraform AWS providers to ~> 5.0

Changes

  • CUMULUS-3258
    • Update all Core integration tests/integrations to be compatible with Orca >=
      v8.1.0 only

Fixed

  • CUMULUS-3319
    • Removed @cumulus/api/models/schema and changed all references to
      @cumulus/api/lib/schema in docs and related models
    • Removed @cumulus/api/models/errors.js
    • Updated API granule write logic to cause postgres schema/db write failures on an individual granule file write to result in a thrown error/400 return instead of a 200 return and a 'silent' update of the granule to failed status.
    • Update api/lib/_writeGranule/_writeGranulefiles logic to allow for schema failures on individual granule writes via an optional method parameter in _writeGranules, and an update to the API granule write calls.
    • Updated thrown error to include information related to automatic failure behavior in addition to the stack trace.
Assets 8