fix(M4Pro): add AWS_CA_BUNDLE for corporate SSL proxy - #7
Conversation
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Zsh Startup Time
Details
| Benchmark suite | Current: a597e9c | Previous: 4e6f0f7 | Ratio |
|---|---|---|---|
zsh -i -c exit |
69.75 ms (17.29 ms) |
37.2 ms (2.41 ms) |
1.87 |
This comment was automatically generated by workflow using github-action-benchmark.
- AWS CLI (Python-based) uses AWS_CA_BUNDLE env var to specify the CA certificate path - SSL_CERT_FILE also works, but AWS_CA_BUNDLE is preferred per AWS official documentation
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Zsh Startup Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.50.
| Benchmark suite | Current: a597e9c | Previous: 4e6f0f7 | Ratio |
|---|---|---|---|
zsh -i -c exit |
69.75 ms (17.29 ms) |
37.2 ms (2.41 ms) |
1.87 |
This comment was automatically generated by workflow using github-action-benchmark.
1 participant
Issue
fixes #6
Changes
hosts/M4Pro/default.nixにAWS_CA_BUNDLE環境変数を追加aws sso login時のCERTIFICATE_VERIFY_FAILEDエラーを解消Verification
Additional Notes
AWS CLI (Python ベース) は
AWS_CA_BUNDLE環境変数で CA 証明書パスを指定する。SSL_CERT_FILEでも動作するが、AWS 公式ドキュメントに従い専用の変数を使用。