From 09dd4ba0fbfa8d29f746c4408f8231804f185dbc Mon Sep 17 00:00:00 2001 From: Arjan Singh Bal <46515553+arjan-bal@users.noreply.github.com> Date: Tue, 8 Apr 2025 14:32:55 +0530 Subject: [PATCH] testdata: Wrap lines to 80 columns in markdown file (#8235) --- testdata/spiffe_end2end/README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/testdata/spiffe_end2end/README.md b/testdata/spiffe_end2end/README.md index 9bb52b4c2..e2ca44350 100644 --- a/testdata/spiffe_end2end/README.md +++ b/testdata/spiffe_end2end/README.md @@ -3,17 +3,17 @@ and `client_spiffebundle.json` are generated with the `generate.sh` and `generate_intermediate.sh` script in this directory. These comprise a root trust certificate authority (CA) that signs two -certificates - `client_spiffe.pem` and `server_spiffe.pem`. These are valid SPIFFE -certificates (via the configuration in `spiffe-openssl.cnf`), and the +certificates - `client_spiffe.pem` and `server_spiffe.pem`. These are valid +SPIFFE certificates (via the configuration in `spiffe-openssl.cnf`), and the `*_spiffebundle.json` files are SPIFFE Bundle Maps for the client and server respectively. -The SPIFFE trust bundle map files (`*_spiffebundle.json`) are manually created for -end to end testing. The `server_spiffebundle.json` contains the `foo.bar.com` -trust domain (only this entry is used in e2e tests) matching URI SAN of -`client_spiffe.pem`, and the CA certificate is `ca.pem`. The client -`spiffebundle.json` file contains `example.com` trust domain matching the URI SAN -of `server_spiffe.pem`, and the CA certificate there is also `ca.pem`. +The SPIFFE trust bundle map files (`*_spiffebundle.json`) are manually created +for end to end testing. The `server_spiffebundle.json` contains the +`foo.bar.com` trust domain (only this entry is used in e2e tests) matching URI +SAN of `client_spiffe.pem`, and the CA certificate is `ca.pem`. The client +`spiffebundle.json` file contains `example.com` trust domain matching the URI +SAN of `server_spiffe.pem`, and the CA certificate there is also `ca.pem`. `leaf_and_intermediate_chain.pem` is a certificate chain whose leaf is a valid SPIFFE cert that is signed by an intermediate CA (`intermediate_ca.pem`). The