When you click "Export Latest" and select either "STIX 2.0 Bundle" or "STIX 2.1 Bundle" the client/frontend makes a call to the REST API:
POST /api/release-tracks/:id/snapshots/latest?include=all&stixVersion=2.1&format=bundle
resulting in a 400 response:
{"message":"Invalid include parameter","parameterName":"include"}
This option was intended to be a tier selector to specify whether members, staged, candidates, quarantine, or all objects should be included in the bundle.
The query parameter is still appearing in the rendered Swagger/OpenAPI documentation.
This should be removed from both the frontend and backend. Deterministic graph manifest generation does not currently account for conditionally pulling in additional non-member objects. Bringing in candidates and/or staged objects would require dynamically recomputing secondary objects which is exactly what we are trying to move away from.
This will require a corresponding change to the backend code.
When you click "Export Latest" and select either "STIX 2.0 Bundle" or "STIX 2.1 Bundle" the client/frontend makes a call to the REST API:
resulting in a 400 response:
This option was intended to be a tier selector to specify whether members, staged, candidates, quarantine, or all objects should be included in the bundle.
The query parameter is still appearing in the rendered Swagger/OpenAPI documentation.
This should be removed from both the frontend and backend. Deterministic graph manifest generation does not currently account for conditionally pulling in additional non-member objects. Bringing in candidates and/or staged objects would require dynamically recomputing secondary objects which is exactly what we are trying to move away from.
This will require a corresponding change to the backend code.