fix(ci): set two stages for insecure and secure images#177
Draft
fegmorte wants to merge 15 commits into
Draft
Conversation
Vulnerability Scan ResultsDetails |
fix(ci): fix folder name fix(ci): fix workspace dependencies fix(ci): fix workspace dependencies fix(ci): fix workspace dependencies fix(ci): fix workspace dependencies fix(ci): fix workspace dependencies fix(ci): build without insecure flags fix(ci): build without insecure flags and fix cargo core service fix(ci): build without insecure flags and fix cargo core service fix(ci): fix kms-core-client path
fegmorte
force-pushed
the
fred/2712/implement-secure-release
branch
from
0bff164 to
7f8e1cb
Compare
Consolidated Tests Results 2026-04-17 - 17:52:35Test Results
Details
Flaky Testsclient::tests::threshold::public_decryption_tests::test_decryption_threshold::case_1 test-reporter: Run #4057
🎉 All tests passed!TestsView All Tests
Flaky Tests
Github Test Reporter by CTRF 💚 🔄 This comment has been updated |
fegmorte
force-pushed
the
fred/2712/implement-secure-release
branch
from
efb69b7 to
5453e37
Compare
…ai/kms into fred/2712/implement-secure-release
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| - name: Checkout Project KMS | ||
| uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0 | ||
| with: | ||
| token: ${{ secrets.BLOCKCHAIN_ACTIONS_TOKEN }} |
|
🚀 Preview deployment is deployed in "thresholdWithEnclave" mode You can now port-forward the kms-core to run your tests locally against the preview deployment. Connect to the Tailscale cluster zws-dev: tailscale configure kubeconfig tailscale-operator-zws-dev.diplodocus-boa.ts.netPort-forward the kms-core services to run your tests locally: kubectl port-forward svc/kms-core-1-core-1 -n kms-ci-fegmorte-177 50100:50100 & \
kubectl port-forward svc/kms-core-2-core-2 -n kms-ci-fegmorte-177 50200:50100 & \
kubectl port-forward svc/kms-core-3-core-3 -n kms-ci-fegmorte-177 50300:50100 & \
kubectl port-forward svc/kms-core-4-core-4 -n kms-ci-fegmorte-177 50400:50100 &Copy config.toml from core-client to ./core-client/config/client_local_kind_threshold.toml kubectl cp kms-ci-fegmorte-177/kms-core-client-0:/app/kms-core-client/config.toml ./core-client/config/client_local_kind_threshold.toml && \
sed -i '' -E 's|address = "(http://)?kms-core-([0-9]+)-[^:]+:50100"|address = "http://localhost:50\200"|' ./core-client/config/client_local_kind_threshold.toml🚀 And launch your tests: cargo nextest run --test kubernetes_test_threshold --profile ci --no-fail-fast --features="kind_tests"You can connect to the core-client with: kubectl exec kms-core-client-0 -n kms-ci-fegmorte-177 -it -- /bin/bashClose your port-forwarding with: pgrep -f "kubectl port-forward" | xargs -n 1 kill |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
Issue ticket number and link
PR Checklist
I attest that all checked items are satisfied. Any deviation is clearly justified above.
chore: ...).TODO(#issue).unwrap/expect/paniconly in tests or for invariant bugs (documented if present).devopslabel + infra notified + infra-team reviewer assigned.!and affected teams notified.Zeroize+ZeroizeOnDropimplemented.unsafe; if unavoidable: minimal, justified, documented, and test/fuzz covered.Dependency Update Questionnaire (only if deps changed or added)
Answer in the
Cargo.tomlnext to the dependency (or here if updating):More details and explanations for the checklist and dependency updates can be found in CONTRIBUTING.md