You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
- Prelude to mega robust product.
- New `k8s.core_v1` release candidate.
- Amended query supporting robot test `K8S Nodes Select Leveraging` JSON Path for updated `k8s.core_v1 interface.
- Send kill signal to destroy al web servers in CI.
Copy file name to clipboardExpand all lines: docs/CICD.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ Summary:
7
7
- At present, PR checks, build and test are all performed through [.github/workflows/go.yml](/.github/workflows/go.yml).
8
8
- Releasing over various channels (website, homebrew, chocolatey...) is performed manually.
9
9
- The strategic state is to split the functions: PR checks, build and test; into separate files, and migrate to use [goreleaser](https://goreleaser.com/).
10
+
- Should take the hint from docker to [speed up multi-platform builds using multiple runners](https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners).
10
11
11
12
12
13
## Secrets
@@ -15,3 +16,7 @@ In lieu of a full implementation of [github actions best practices](https://secu
15
16
- Pull request checks use [the pull_request event](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request), as per [best practices](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
16
17
- Integration test steps, which require secrets, leverage [the github context](https://docs.github.com/en/actions/learn-github-actions/contexts#github-context) to avoid running where secrets are absent.
17
18
- Therefore, external fork PRs, which are the community contribution model, do not run integration tests. Strategically, we may funnel community contribution though a staging branch and/or adopt release branches. This is not an urgent consideration, and we shall decide after some reflection.
19
+
20
+
## API mocking
21
+
22
+
According to [this swagger-codegen example](https://github.com/swagger-api/swagger-codegen/blob/master/bin/python-flask-petstore.sh), it is not overly difficult to generate python mocks from openapi docs. This can then be used for credible regression testing against new provider docs and certainly the relationship of endpoints to stackql resources. Know weakness: will not detect defective transform from source (eg: MS-graph, AWS) to openapi.
0 commit comments