release/1.5.0 (2026-01-08)
release/1.6.0 (2026-01-07)
Requirements:
- As a user, I want to receive an alert when my registry credentials are readable by someone else than myself #424
- As a node operator, I want the the registry schema to update autonomously / dynamically when new data is ingested. #113
Improvements:
- Document and script the monthly legacy registry statusing #460
Defects:
- Some properties return "null" values #456 [s.medium]
- lid and pds:Identification_Area.pds:logical_identifier do not behave the same in the API #423 [s.medium]
- Some of product urn:nasa:pds:lro_diviner_derived2::1.0's fields are not indexed #422 [s.high]
- Error
FIPS mode: only SunJSSE TrustManagers may be used#440 [s.high] - Registry is not accepting date time with leap second, e.g.
2015-06-30T23:59:60.862Z#404 [s.high] - members of GEO bundle/collection collection not found #403 [s.high]
- CSV response not returning the values associated with
fieldsargument #380 [s.medium] - product has date for sweeper index but is listed as not indexed #375 [s.medium]
Other closed issues:
- Troubleshoot SBN 403 Error #414
- Add the --legacy-sync command option to the EN sweeper in production #390
- Document password rotation requirements #320
- Update registry documentation #288
- Respond to User Questions Regarding Supporting Migration to OpenSearch Serverless #275
v1.4.0 (2025-07-16)
release/1.4.0 (2025-07-16)
Requirements:
- As a node user, I want to have multiple cognito groups and still have the main cognito node group to be effective #396
- As a user, I want to have read-only access to all registry indexes #350
- As a data manager, I want to query OpenSearch Serverless from the command-line #273 [s.critical]
Improvements:
- Document the refresh rate of OpenSearch #361
- Fix GEO node products which ops:Harvest_Info/ops:node_name: geo #360
- Recreate PDS EN Registry from scratch and load only necessary data #352
- Migrate registry-harvest-service documentation #78
Defects:
- Registry return authorization error for ATM node #369 [s.critical]
- Update terraform to use port 443 not port 80 #365 [s.critical]
- Data products duplicated across en-registry and other node registries #351 [s.high]
- Getting "blocked by: maximum OCU capacity reached" errors when harvesting #340 [s.critical]
- SBN user no longer able to access test registry #336 [s.critical]
- GEO index does not work, appears to be corrupted #331 [s.critical]
- AOSS 500/502 responses repeatedly observed under heavy load #329 [s.high]
- Secret detection is broken on branch titan_treks_utility_script #292 [s.medium]
- harvest created archive_status as an array and registry-mgr updates it as a string #276 [s.medium]
- Missing NAIF from Legacy Dashboard #234 [s.low]
Other closed issues:
- Investigate the opensearch serverless scale out/down parameters #397
- Clean test suite to un-skip test skipped after multitenant migration #378
- Respond to Registry SIA review from SAs #364
- Complete security vulnerability assessment for registry #356
- Update Registry configuration to support issues with IMG user(s) #337 [s.critical]
- Document in the wiki how the authorization on opensearch are managed #334
- Reindex MCP Prod ATM registry index with corrected mappings #339
- Investigate what the number of property per discipline node was at migration time #332
- Onboard Irma from ATM node #325
- Add reference links to LOLA data #316
- As an administrator of the registry, I don't want ENG operator loading data to have administration authorizations #309
- Finalize Cognito configuration in production for the Registry #307
- Add Lola PDS4 script #305
- Propose options to integrate Trek footprints to PDS products #295
- Generalize the treks util to all the Treks services #294
- Make sure all the useful Treks links are used/referenced in the PDS4 LAbel #291
- Load the GIS Treks products in a local registry #289
- Meet with Treks, MMGIS and GEOSTAC to discuss the PDS GIS activity #287
- Design/Develop the initial GIS demo #286
- Create the PDS4 service labels for the dataset served by GIS services #285
- Create GIS collection PDS4 label #284
- Create context product unique identifier #283
- Managed OpenSearch Snapshots #282
- Migrate and fix types mismatches in registry mappings from all node cluster to OpenSearch serverless #280
- Create snapshots of production OpenSearch clusters prior to shutdown #278
- Copy data necessary for web mod efforts to search-en registry prior to shutdown #277
- Deploy Multi-tenant Registry to test #272
- Deploy Multi-tenant Registry to production and sync data #271
- The migrated documents on opensearch serverless have a generated _id #270
- Upgrade docker compose as needed for the multitenant setup #269
- Setup API Gateway - OpenSearch Serverless Authentication #256
- Create Lambda Authorizer for Read Access - OpenSearch Serverless Authentication #255
- Create Lambda Authorizer for Write Access - OpenSearch Serverless Authentication #254
- Setup Cognito Identity Pool #253
- Create IAM Roles for OpenSearch Serverless Authentication #252
- Setup Cognito User Pool #251
- Setup monitoring for Domain Notifications for all OpenSearch Domains in AWS #233
- Registry-Sweepers Multiple Updates Statements Detected - NOT retry-related #225
- Initial OpenSearch Serverless Setup and Deployment in MCP #223
- Add registry costs to the PDS EN Cloud spreadsheet #218
- Write a migration plan to multitenant registry #217
- Design scalable, multi-tenant opensearch #212
- B14.0 Update postman test suite with bug fixes for current build #201
- B14.0 Update the postman test suite with all the requirement tests #200
- Enable I&T to use and update registry-api automated tests #199
- Design authorization handshake with Cognito, API Gateway, and Lambda for multi-tenancy approach #179
- Revise documentation to be more clear about what is suitable for operational vs. development purposes #95
v1.3.1 (2023-11-16)
release/1.3.1 (2023-11-16)
Requirements:
- As a user, I want the registry to have 99.9999999% uptime #176
Other closed issues:
- Assist with DUM infra setup in MCP #238
- Write documentation and Training for Registry monitoring #224
- Setup OIDC Authentication for MCP #222
v1.3.0 (2023-10-11)
Requirements:
- As a system, I can support up to 25 simultaneous writes from Harvest #226
- As an operator, I want to be notified of when Registry storage capacity exceeds 75% capacity. #211
- As a manager, I want to see the progress of data sets ingested into registry vs. legacy registry #168
Defects:
- Increase disk space for ATM opensearch #213 [s.critical]
- Provenance script failing on production registry #180 [s.high]
Other closed issues:
- Improve test automation with postman #228
- Fix lambda filters for registry-sweepers and registry-api #227
- Create a new login for IMG Tariq #216
- Use Richard's test dataset for the integrated postman tests in docker compose #198
- incorporate registry-sweepers as dependency in the docker compose deployment script #197
- Harvest OREX dataset from SBN-PSI web #196
- Add provenance script to the lucidchart AWS deployment diagram #195
- Update cloud-front / ELB configuration to forward request headers to registry-api #191
- Rework Registry+API Architecture Diagram in LucidChart #189
- Run registry-manager to set all archive status to archived on all the collections for ATM and NAIF node #182
- Add CloudWatch event for monitoring provenance script failure #167
v1.2.0 (2023-04-18)
Requirements:
- As a user, I want to all metadata attributes to be searchable #153
- As a user, I want to view dashboard report of bundles with archive status and other tracking information #130
- Update documentation to include explicit example of how to query staged data #100
- As a user, I want to indicate a product has been superseded #52
Improvements:
- Update docs to be more clear that there is a required next step after data ingestion #139
Defects:
- Expo system doesn't use latest images published to Docker Hub #175
- ref_collection_lidvid field in some node registries populated using older versions of registry loader tools create string fields in the schema vs. the expected list types #159 [s.medium]
- TLS termination listening on wrong port #150 [s.medium]
- Expo Registry fails to start #149 [s.medium]
- OpenSearch service of Registry won't start on Linux #146 [s.high]
- Harvest is throwing errors of "Forbidden index write" #132 [s.high]
- registry-manager won't set archive-status on some collections #97 [s.high]
Other closed issues:
- Update Terraform scripts to support multi-tenancy #188
- Check that none of the Opensearch servers, besides NAIF have archive_status==null #183
- Add documentation on the auth.cfg file for the registry tools users #170
- Schedule provenance script #160
- Integrate new
provenance.pyscript into operational deployment to tag products with Provenance information #141 - Integrate new
provenance.pyscript into integration tests to tag products with Provenance information #140
v1.1.3 (2022-12-14)
Defects:
- follow on to #118, registry-manager still unable to change archive status on bundle contents #136 [s.high]
- archive status value was not changed on bundle's contents #118 [s.high]
v1.1.2 (2022-11-10)
v1.1.1 (2022-10-26)
Defects:
v1.1.0 (2022-09-21)
Defects:
v1.0.2 (2022-08-03)
Defects:
- when docker compose starts, registry-api docker is missing curl #69 [s.critical]
- Scalable Harvest does not replace file paths with the appropriate URL prefix #64 [s.high]
- docker compose int-registry-batch-loader failure #41 [s.medium]
Other closed issues:
- Update README to reflect best practices of other PDS repositories #53 [s.high]
- Develop script to update existing registry metadata per B12.1 metadata modifications #43
- Plan and strategize how to migrate to OpenSearch deployments #54
- Add supersede / update product version functionality in Registry Manager #56
- Add new "alternate_ids" field to Elasticsearch schema #59
- Design the PDS4 definition for describing superseded LIDs via product metadata #57
v1.0.1 (2022-05-03)
v1.0.0 (2022-05-03)
Requirements:
- Upgrade the initialization of the ES/OS database following latest upgrade of components #31
- As a developer, I want to include supplemental file data sizes in the registry #112
- As a node operator, I want to ingest metadata regarding secondary collections that belong to a bundle. #109
- As a node operator, I want to ingest metadata regarding secondary products that belong to a collection. #108
- As a node operator, I want actionable, user-friendly error messages for registry schema failures #110
- The service shall allow deletion of registered artifacts #103
- The service shall provide a means identifying relationships between artifact registrations #104
- As a registry user, I want to ingest supplemental metadata from Product_Metadata_Supplemental. #121
* This Changelog was automatically generated by github_changelog_generator