Update certificates and add documentation.

[dbudziwojskiNR]

Description

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• New feature / enhancement (non-breaking change which adds functionality)
• Security fix
• Bug fix (non-breaking change which fixes an issue)

Checklist:

• Add changelog entry following the contributing guide
• Documentation has been updated
• This change requires changes in testing:
  • unit tests
  • E2E tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.94%. Comparing base (24a8793) to head (34933c6).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1064   +/-   ##
=======================================
  Coverage   67.94%   67.94%           
=======================================
  Files          55       55           
  Lines        3379     3379           
=======================================
  Hits         2296     2296           
  Misses        904      904           
  Partials      179      179           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[juanjjaramillo]

Can you please rephrase this sentence? It sounds you are replacing contents of a file with its own content, which is a noop. Also, can you explain why not simply copying the key file? There must be a good reason for that

[dbudziwojskiNR]

I see where the confusion can arise. I'll reword it to use copy instead of replace. Regarding the key file, the engineer needs to copy the CA cert, not the key. The CA key is the private key used to sign certs so committing that would would be bad, hence the warning. I'll clarify this.

[dbudziwojskiNR]

Thoughts on this: Copy rootCA.pem into src/integration/sink/testdata replacing the expired cert. Do NOT copy rootCA-key.pem file.

[juanjjaramillo]

So where do you store the key?