update testing/environments/docker/elasticsearch/pki certs#46337
update testing/environments/docker/elasticsearch/pki certs#46337AndersonQ merged 2 commits intoelastic:mainfrom
testing/environments/docker/elasticsearch/pki certs#46337Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
f8a8541 to
a77fc21
Compare
|
Thanks for fixing this! I’m wondering if it would make sense to generate these files as part of CI so they’re always up to date. Otherwise, we’ll run into the same issue later and have to regenerate them. If that’s not possible, what’s the validity period of the certs you generated? |
5 yeas, it's on the "how to test this PR"
I was thinking about it as well. I rather have them generated on the fly as well. But first I'd like to unblock CI. |
- replace the expired certificates with certificated valid for 5 years - restore previous naming - update sha256 on certificate pinning tests - use keys in DER format
a77fc21 to
c146343
Compare
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
LGTM. I confirmed locally that the new certs are valid for 5 years. |
testing/environments/docker/elasticsearch/pki certstesting/environments/docker/elasticsearch/pki certs
- replace the expired certificates with certificated valid for 5 years - restore previous naming - update sha256 on certificate pinning tests - use keys in DER format (cherry picked from commit c02858b) # Conflicts: # libbeat/tests/integration/ca_pinning_test.go # testing/environments/docker/elasticsearch/pki/ca/ca.crt # testing/environments/docker/elasticsearch/pki/ca/ca.key # testing/environments/docker/elasticsearch/pki/elasticsearchssl/elasticsearchssl.crt # testing/environments/docker/elasticsearch/pki/elasticsearchssl/elasticsearchssl.key
|
@Mergifyio backport 8.19 |
✅ Backports have been createdDetails
|
- replace the expired certificates with certificated valid for 5 years - restore previous naming - update sha256 on certificate pinning tests - use keys in DER format (cherry picked from commit c02858b)
- replace the expired certificates with certificated valid for 5 years - restore previous naming - update sha256 on certificate pinning tests - use keys in DER format (cherry picked from commit c02858b) Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
Proposed commit message
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
How to test this PR locally
Related issues