influxdata / influxdata/openapi
Run OpenAPI PRs against the UI's monitor-ci tests
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
This issue is being created to help unpin the UI from SHA-specific openAPI versions and rely upon master. A big hang-up to doing this originally was the fear that a breaking change to a yaml file would break the UI immediately in all environments without being caught beforehand. If we were able to integrate monitor-ci tests to the openapi PRs, we could be more confident that any changes that get merged into the main branch are kosher, removed the UI's need to constantly update the SHA that is being referenced to generate functions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the UI's monitor-ci tests and the current SHA-based OpenAPI reference. Determine how OpenAPI pull requests could run those tests before merging; done means changes can be validated against the UI while allowing it to rely on the main OpenAPI branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100