/explore
|
You are here 
|
navendu.me | ||
| | | | |
janik6n.net
Run security scans on Terraform and OpenTofu project with Trivy and GitHub Actions |
|
| | | | | ||
| | | | |
code.dblock.org
The OpenSearch API specification is authored in OpenAPI and used to auto-generate OpenSearch language clients. I wanted to know how much of the API was described in it vs. the actual API implemented in the default distribution of OpenSearch that includes all plugins. To do so, I have exposed an iterator over REST handlers in OpenSearch core, and wrote a plugin that rendered a very minimal OpenAPI spec at runtime. All that was left was to compare the manually authored OpenAPI spec in opensearch-api-specification to the runtime one, added in opensearch-api-specification#179. The comparison workflow output a total and relative number of APIs described. |
|
| | | | | ||
| | | | |
kinoshita.eti.br
Normally when you add test coverage to a GitHub repository, the reporting part boils down to a simple call to some API that will post to a third-party external service like Coveralls or Codecov. Many are already on the GitHub Actions Market Place and a few lines of YAML are enough. A Codecov coverage report We had to report the test coverage of a private GitHub repository of a project I am working on at the moment, that could not have integration with other services besides GitHub. |
|
| | | | | ||
| | | | |
dotnet.github.io
|
|
| | | |||
