/explore
|
You are here 
|
kinoshita.eti.br | ||
| | | | |
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. | |
| | | | |
fusectore.dev
|
|
| | | | | During one of my assignments, I worked with GitHub Actions pretty much every day. I implemented workflows, created new actions, and helped people migrate their projects from jenkins to actions. As much as I like actions and I like them a lot there are some things that caught me off guard. I have collected some of these things, both for other people to let them know, and for myself as a future reference. How well do you know actions? Can you answer all of these questions correctly? Assume that all YA... | |
| | | | |
dotnet.github.io
|
|
| | | |||
