Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: test api responses against openapi spec #327

Merged
merged 5 commits into from
Mar 8, 2024

Conversation

stephenkilbourn
Copy link
Contributor

What?

Currently, we test the api endpoints to ensure the correct response code (e.g. 200). This is a POC to use the open api validator to validate the response body against the stac open api spec. Currently, the docs are showing the response for these two endpoints as just any string. I've used a subset of the open api spec at https://api.stacspec.org/ to manually enter in a schema for now.

Testing?

these tests can be run locally with the existing shell script: ./scripts/run-local-tests.sh

@stephenkilbourn stephenkilbourn changed the title DRAFT: test api responses against openapi spec chore: test api responses against openapi spec Mar 8, 2024
@stephenkilbourn stephenkilbourn merged commit 905d4c0 into develop Mar 8, 2024
4 checks passed
@anayeaye anayeaye deleted the validate-api branch March 12, 2024 21:19
anayeaye added a commit that referenced this pull request Mar 12, 2024
…n improvements (#330)

## Added
* Optional `VEDA_SUBNET_IDS` Allows users to specify the subnet IDs to
be used for the database. (#329, #323)
* Test api responses against openapi spec (#327)
* Configuration updated for deploying new encrypted RDS instances from
encrypted snapshots (#326)

## CI
* Update version of GitHub actions
* Updates needed to deploy using `veda-deploy` (#324)
* exports additional specific cloudformation outputs needed for
downstream dependent stacks deployed in sequence
* externally triggered composite action parses required cdk outputs from
upstream stacks
botanical added a commit that referenced this pull request May 6, 2024
### Breaking
- #356

#### Breaking changes notes
Breaking: `VEDA_COGNITO_DOMAIN` configuration now required along with
one time administrator step to update existing user pool client allowed
callback urls with the ingest-api's URL

### Added
- #342
- #330
- #323

### Changed/Updated
- #355
- #340

### Fixed

1. - #367
2. - #365
3. - #361
4. - #360
5. - #358
8. - #345
9. - #344
12. - #339
13. - #338
14. - #337
15. - #335
16. - #334
17. - #331
20. - #329
21. - #327
22. - #326
23. - #325
24. - #324
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants