@cumulus/logger
Advanced tools
Changelog
[v16.0.0] 2023-05-09
When updating directly to v16 from prior releases older that V15, please make sure to read through all prior release notes.
Notable migration concerns since the last PI release version (11.1.x):
files_granules_cumulus_id_index
to the
files
table may require manual steps depending on load.This release includes updates that remove existing DynamoDB tables as part of release deployment process. This release cannot be properly rolled back in production as redeploying a prior version of Cumulus will not recover the associated Dynamo tables.
Please read the full change log for RDS Phase 3 and consult the RDS Phase 3 update documentation
As part of the work on CUMULUS-3072, we have added a required header for the granule PUT/PATCH endpoints -- to ensure that older clients/utilities do not unexpectedly make destructive use of those endpoints, a validation check of a header value against supported versions has been implemented.
Moving forward, if a breaking change is made to an existing endpoint that requires user updates, as part of that update we will set the current version of the core API and require a header that confirms the client is compatible with the version required or greater.
In this instance, the granule PUT/PATCH
endpoints will require a Cumulus-API-Version
value of at least 2
.
curl --request PUT https://example.com/granules/granuleId.A19990103.006.1000\
--header 'Cumulus-API-Version: 2'\
--header 'Content-Type: application/json'\
--header 'Authorization: Bearer ReplaceWithToken'\
--data ...
Users/clients that do not make use of these endpoints will not be impacted.
bulk-operation
Lambda should provide collectionId and granuleId e.g. { granuleId: xxx, collectionId: xxx }ReconciliationReportsTable
from dbIndexer
lambda@cumulus/api/ecs/async-operation/*
asyncOperationsStart
callsgetFilesExistingAtLocation
from api granules model to api/lib, update granules put
endpoint to remove model referencesPOST
endpointPUT
endpointDELETE
endpointPUT
endpointrulesModel
to rulesHelper
api/models/collections.js
to api/lib/utils.js
sfEventSqsToDbRecords
lambdacreate
in the db
model for Rules
to return an array of objects containing all columns of the created record.rulesModel
to rulesHelper
DELETE
endpointPUT
endpoint@cumulus/api
executeMigrations
lambdagranuleFilesCacheUpdater
lambdadata-persistence
module. This table and
all of its data will be removed on deployment.replaceGranule
to @cumulus/api-client/granules
to add usage of the
updated RESTful PUT logic@cumulus/api-client/granules.bulkOperation
to remove ids
parameter in favor of granules
parameter, in the form of a
@cumulus/types/ApiGranule
that requires the following keys: [granuleId, collectionId]
pg
to v8.10.x
xml2js
to v0.5.0
xml2js
in saml2-js
to
v0.5.0
skip
or error
to stop retrying
after receiving a 404 Not Found Response Error from the cumulus-api
.parallel
package, as timeouts were not resulting in
integration test failure@cumulus/cmrjs/cmr-utils.getGranuleTemporalInfo
to handle the error when the cmr file s3url is not availablesfEventSqsToDbRecords
lambda to return partial batch failure,
and only reprocess messages when cumulus message can't be retrieved from the execution events.@cumulus/cumulus-message-adapter-js
to 2.0.5
for all cumulus tasksChangelog
[v15.0.4] 2023-06-23
pg
to v8.10.x
skip
or error
to stop retrying
after receiving a 404 Not Found Response Error from the cumulus-api
.parallel
package, as timeouts were not resulting in
integration test failure@cumulus/cmrjs/cmr-utils.getGranuleTemporalInfo
to handle the error when the cmr file s3url is not availablesfEventSqsToDbRecords
lambda to return partial batch failure,
and only reprocess messages when cumulus message can't be retrieved from the execution events.@cumulus/cumulus-message-adapter-js
to 2.0.5
for all cumulus tasksChangelog
[v15.0.3] 2023-04-28
Changelog
[v15.0.2] 2023-04-25
default_log_retention_periods
and cloudwatch_log_retention_periods
to Cumulus modules so they can be used during deployment for configuring cloudwatch retention periods, for more information check here: retention documentChangelog
[v15.0.1] 2023-04-20
xml2js
to v0.5.0
xml2js
in saml2-js
to
v0.5.0
api/lib/distribution.js isAuthBearTokenRequest
to handle non-Bearer authorization headerChangelog
[v15.0.0] 2023-03-10
cumuluss/cumulus-ecs-task
Docker image must be updated to cumuluss/cumulus-ecs-task:1.9.0.
which is built with node:16.19.0-alpine. This can be done by updating the image
property of any tasks defined using the cumulus_ecs_service
Terraform module.44
of cumuluss/async-operation
to Docker Hub.async_operation_image
property of cumulus
module must be updated to pull the ECR image for cumuluss/async-operation:44
.Changelog
[v14.1.0] 2023-02-27
From this release forward Core will be tested against PostgreSQL 11 Existing release compatibility testing was done for release 11.1.8/14.0.0+. Users should migrate their datastores to Aurora PostgreSQL 11.13+ compatible data stores as soon as possible.
Users utilizing the cumulus-rds-tf
module will have upgraded/had their
database clusters forcibly upgraded at the next maintenance window after 31 Jan
2023. Our guidance to mitigate this issue is to do a manual (outside of
terraform) upgrade. This will result in the cluster being upgraded with a
manually set parameter group not managed by terraform.
If you manually upgraded and the cluster is now on version 11.13, to continue
using the cumulus-rds-tf
module once upgraded update following module
configuration values if set, or allow their defaults to be utilized:
parameter_group_family = "aurora-postgresql11"
engine_version = 11.13
When you apply this update, the original PostgreSQL v10 parameter group will be removed, and recreated using PG11 defaults/configured terraform values and update the database cluster to use the new configuration.
PUT
endpoint. In future releases the PUT
endpoint will be replaced with valid PUT logic
behavior (complete overwrite) in a future release. The existing PUT
implementation is deprecated and users should move all existing usage of
PUT
to PATCH
before upgrading to a release with CUMULUS-3072
.CUMULUS-3033
granuleEsQuery
to properly terminate if body.hit.total.value
is 0.The getLambdaAliases
function has been removed from the @cumulus/integration-tests
package
The getLambdaVersions
function has been removed from the @cumulus/integration-tests
package
CUMULUS-3117
@cumulus/es-client/indexer.js
to properly handle framework write
constraints for queued granules. Queued writes will now be properly
dropped from elasticsearch writes along with the primary datastore(s) when
write constraints applyCUMULUS-3134
CUMULUS-3148:
CUMULUS-3149
/granules/bulkDelete
endpoint to take the
following configuration keys for the bulkDelete:
concurrency
, and generally should not be
changed unless troubleshooting performance concerns.CUMULUS-3142
CUMULUS-3181
sqsMessageRemover
lambda to correctly retrieve ENABLED sqs rules.CUMULUS-3189
cumulus-process
and cumulus-message-adapter-python
versions to
support pip 23.0CUMULUS-3196
createServer
initialization outside the s3-credentials-endpoint
lambda
handler to reduce file descriptor usageREADME shell snippets better support copying
CUMULUS-3111
{ version: 2 }
2
@cumulus/api-client
packages to use PATCH
protocol for existing
granule PUT
calls, this change should not require user updates for
api-client
users.
@cumulus/api-client/granules.updateGranule
@cumulus/api-client/granules.moveGranule
@cumulus/api-client/granules.updateGranule
@cumulus/api-client/granules.reingestGranule
@cumulus/api-client/granules.removeFromCMR
@cumulus/api-client/granules.applyWorkflow
@cumulus/cmr-client
package's token from Echo-Token to Earthdata Login (EDL) token in updateToken method