Skip to content

Commit

Permalink
Update changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
pdsen-ci committed Jul 29, 2024
1 parent c9408ff commit e3162f1
Showing 1 changed file with 54 additions and 2 deletions.
56 changes: 54 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,36 @@
# Changelog

## [«unknown»](https://github.com/NASA-PDS/registry-api/tree/«unknown») (2024-03-18)
## [«unknown»](https://github.com/NASA-PDS/registry-api/tree/«unknown») (2024-07-29)

[Full Changelog](https://github.com/NASA-PDS/registry-api/compare/v1.4.1...«unknown»)

**Requirements:**

- As a user, I want to get all the products for a specific PDS4 product class [\#511](https://github.com/NASA-PDS/registry-api/issues/511)
- As a user, I want to receive metadata only in the API responses \(no binary blobs\) [\#497](https://github.com/NASA-PDS/registry-api/issues/497)
- As a user, by default, I want to search for the latest versions of all products on the `/classes/{class}` endpoint unless explicitly requested [\#488](https://github.com/NASA-PDS/registry-api/issues/488)
- As a user, by default, I want to search only for the latest versions of all products on the `/products/{identifier}/member-of/member-of` endpoint [\#487](https://github.com/NASA-PDS/registry-api/issues/487)
- As a user, by default, I want to search for only the latest versions of all products on the `/products/{identifier}/member-of` endpoint [\#486](https://github.com/NASA-PDS/registry-api/issues/486)
- As a user, by default, I want to search for only the latest versions of all products on the `/products/{identifier}/members/members` endpoint [\#485](https://github.com/NASA-PDS/registry-api/issues/485)
- As a user, by default, I want to search for only the latest versions of all products on the `/products/{identifier}/members` endpoint [\#484](https://github.com/NASA-PDS/registry-api/issues/484)
- As a user, I want to filter the products by any available PDS4 property using a combination of comparison, logical, and precedence grouping operators [\#469](https://github.com/NASA-PDS/registry-api/issues/469)
- As a user, I want to get all product versions associated to one lid [\#436](https://github.com/NASA-PDS/registry-api/issues/436)
- As a user, I want to get a product description given a lidvid [\#434](https://github.com/NASA-PDS/registry-api/issues/434)

**Defects:**

- Insufficient scrubbing of user input values prior to logging [\#388](https://github.com/NASA-PDS/registry-api/issues/388) [[s.medium](https://github.com/NASA-PDS/registry-api/labels/s.medium)]
- Cleanup logging of keys [\#387](https://github.com/NASA-PDS/registry-api/issues/387) [[s.medium](https://github.com/NASA-PDS/registry-api/labels/s.medium)]

**Other closed issues:**

- Manage renewal of AWS credentials [\#514](https://github.com/NASA-PDS/registry-api/issues/514)
- Partial implementation of the opensearch serverless queries [\#470](https://github.com/NASA-PDS/registry-api/issues/470)
- ECS Roles for Registry-API [\#429](https://github.com/NASA-PDS/registry-api/issues/429)
- Demo partial implementation on AWS [\#423](https://github.com/NASA-PDS/registry-api/issues/423)
- Demo registry-api with new opensearchclient [\#422](https://github.com/NASA-PDS/registry-api/issues/422)
- Add pds-deep-registry-archive execution to branch testing [\#412](https://github.com/NASA-PDS/registry-api/issues/412)
- Add github action on dev branch push, running registry integration test with docker compose [\#301](https://github.com/NASA-PDS/registry-api/issues/301)

## [v1.4.1](https://github.com/NASA-PDS/registry-api/tree/v1.4.1) (2024-02-29)

Expand Down Expand Up @@ -92,11 +111,13 @@

**Requirements:**

- Remove provenance --reset option [\#310](https://github.com/NASA-PDS/registry-api/issues/310)
- As a user, I want to see available query params in the swagger documentation [\#249](https://github.com/NASA-PDS/registry-api/issues/249)
- Suggest: Return Content-Type application/json by default [\#248](https://github.com/NASA-PDS/registry-api/issues/248)
- As a user, I want to search by any metadata attribute [\#282](https://github.com/NASA-PDS/registry-api/issues/282)
- As a user, I want to know the members of a bundle product [\#223](https://github.com/NASA-PDS/registry-api/issues/223) [[s.high](https://github.com/NASA-PDS/registry-api/labels/s.high)]
- As a user, I want to get application/json response format by default if I request an API url in my browser [\#439](https://github.com/NASA-PDS/registry-api/issues/439)
- As a user, I want to query only the latest versions of products unless explicitly requested [\#441](https://github.com/NASA-PDS/registry-api/issues/441)
- As a user, I want to be able to access the Search API Swagger interface from pds.nasa.gov [\#442](https://github.com/NASA-PDS/registry-api/issues/442)
- the default proposed mime type in swagger-ui.html should be 'application/json' [\#88](https://github.com/NASA-PDS/registry-api/issues/88) [[s.low](https://github.com/NASA-PDS/registry-api/labels/s.low)]

**Defects:**
Expand Down Expand Up @@ -128,6 +149,7 @@

**Other closed issues:**

- Remove provenance --reset option [\#310](https://github.com/NASA-PDS/registry-api/issues/310)
- Establish consistency between how Provenance and the API select \(filter\) documents by archive\_status [\#308](https://github.com/NASA-PDS/registry-api/issues/308)
- If \>1 products with the same LIDVID are registered by different nodes, we should respond with one of them [\#306](https://github.com/NASA-PDS/registry-api/issues/306)
- Update Java params and Docker image to expand JVM memory beyond 50% [\#300](https://github.com/NASA-PDS/registry-api/issues/300)
Expand Down Expand Up @@ -163,6 +185,10 @@

[Full Changelog](https://github.com/NASA-PDS/registry-api/compare/v1.1.10...v1.1.11)

**Requirements:**

- As a user, I want an end-point of each of the PDS4 IM classes of products [\#461](https://github.com/NASA-PDS/registry-api/issues/461)

**Defects:**

- /all suffix returns a message which I don't understand [\#190](https://github.com/NASA-PDS/registry-api/issues/190) [[s.high](https://github.com/NASA-PDS/registry-api/labels/s.high)]
Expand Down Expand Up @@ -298,15 +324,41 @@

**Requirements:**

- As a user, I want to receive error messages when an invalid request is submitted to the API [\#443](https://github.com/NASA-PDS/registry-api/issues/443)
- As a user, I want the API response media types to be compliant with RFC 6838 [\#464](https://github.com/NASA-PDS/registry-api/issues/464)
- As a user, I want to see the version of the API specification in the URL of the service [\#59](https://github.com/NASA-PDS/registry-api/issues/59)
- As a user, I want to get a key-value-pair JSON response [\#444](https://github.com/NASA-PDS/registry-api/issues/444)
- As a user, I want to receive a XML response that contains the PDS4 label metadata in XML format \(application/vnd.nasa.pds.pds4+xml\) [\#440](https://github.com/NASA-PDS/registry-api/issues/440)
- As an API user, I want a CSV response format option [\#445](https://github.com/NASA-PDS/registry-api/issues/445)
- As a user, I want to clearly see which formats are accepted by the API when a 406 error is raised [\#446](https://github.com/NASA-PDS/registry-api/issues/446)
- As an API user, I want to explicitly request the latest version of a product [\#448](https://github.com/NASA-PDS/registry-api/issues/448)
- As a API manager, I want to restrict access to registered products that should not be publicly accessible [\#466](https://github.com/NASA-PDS/registry-api/issues/466)
- As an API user, I want to know how long a request took to complete [\#463](https://github.com/NASA-PDS/registry-api/issues/463)
- As a user, I want to receive a JSON response that contains the PDS4 label metadata in JSON format \(application/vnd.nasa.pds.pds4+json\) [\#450](https://github.com/NASA-PDS/registry-api/issues/450)
- As an API user, I want to be able to use the API for free text search [\#460](https://github.com/NASA-PDS/registry-api/issues/460)
- As an API user, I want to get the latest version of a product, by default [\#449](https://github.com/NASA-PDS/registry-api/issues/449)
- As a user, I want to query for all versions of a product [\#438](https://github.com/NASA-PDS/registry-api/issues/438)
- As a user, I want to have a complete default fields \(for now at least\) [\#155](https://github.com/NASA-PDS/registry-api/issues/155)
- As a user, I want the end-point /api to redirect to the API documentation [\#63](https://github.com/NASA-PDS/registry-api/issues/63)
- As a user, I want the /products end point to work for any class of products [\#64](https://github.com/NASA-PDS/registry-api/issues/64)
- As a user, I want specific end points for products which are not collections or bundles [\#65](https://github.com/NASA-PDS/registry-api/issues/65)
- As a user, I want to know why my query syntax is invalid [\#66](https://github.com/NASA-PDS/registry-api/issues/66)
- As an operator, I want to have a wrapper script for starting up the API service [\#67](https://github.com/NASA-PDS/registry-api/issues/67)
- As an API user, I want to search using URL parameters [\#462](https://github.com/NASA-PDS/registry-api/issues/462)
- As a developer, I never want the label blob to be returned [\#467](https://github.com/NASA-PDS/registry-api/issues/467)
- As an API user, I want to handle long-running queries that take \>10 seconds. [\#68](https://github.com/NASA-PDS/registry-api/issues/68)
- As an API user, I want an average query response time of 1 second for q=\* queries [\#69](https://github.com/NASA-PDS/registry-api/issues/69)
- As an API user, I want to specify whether I get the latest or all versions of a product [\#447](https://github.com/NASA-PDS/registry-api/issues/447)
- As an API user, I want to search by a temporal range as an ISO-8601 time interval. [\#465](https://github.com/NASA-PDS/registry-api/issues/465)
- As an API user, I want to get an XML response [\#456](https://github.com/NASA-PDS/registry-api/issues/456)
- As an API user, I want to get only the fields I explicitly requested [\#459](https://github.com/NASA-PDS/registry-api/issues/459)
- As a user, when I request specific fields I want to get records which have at least one of these fields [\#455](https://github.com/NASA-PDS/registry-api/issues/455)
- As an API user, I want to know the Bundle for a given Collection. [\#452](https://github.com/NASA-PDS/registry-api/issues/452)
- As an API user, I want to know the Collection\(s\) for a given Product. [\#451](https://github.com/NASA-PDS/registry-api/issues/451)
- As an API user, I want to know the Bundle for a given Product. [\#454](https://github.com/NASA-PDS/registry-api/issues/454)
- As an API user, I want to know the Product\(s\) that belong to a given Bundle. [\#453](https://github.com/NASA-PDS/registry-api/issues/453)
- As an API user, I want to know the children and ancestors of bundle, collections, and products [\#458](https://github.com/NASA-PDS/registry-api/issues/458)
- As an API user, I want to perform a search using wildcards [\#457](https://github.com/NASA-PDS/registry-api/issues/457)

**Improvements:**

Expand Down

0 comments on commit e3162f1

Please sign in to comment.