Skip to content

[1.16] ci: update actions/cache v4.0.2 -> v4.2.0#29870

Closed
tvoran wants to merge 10 commits intorelease/1.16.xfrom
docs/update-1.16-cache-action
Closed

[1.16] ci: update actions/cache v4.0.2 -> v4.2.0#29870
tvoran wants to merge 10 commits intorelease/1.16.xfrom
docs/update-1.16-cache-action

Conversation

@tvoran
Copy link
Copy Markdown
Member

@tvoran tvoran commented Mar 7, 2025

@tvoran tvoran requested a review from a team as a code owner March 7, 2025 19:01
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Mar 7, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 7, 2025

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 7, 2025

Build Results:
All builds succeeded! ✅

ryancragun
ryancragun previously approved these changes Mar 7, 2025
tvoran and others added 2 commits March 14, 2025 14:09
)

* Update an expired certificate within the cert-auth test fixtures

* Update additional vault-diagnose tests with an expired cert using pkihelper
@tvoran tvoran requested a review from a team as a code owner March 14, 2025 22:04
stevendpclark and others added 6 commits March 14, 2025 15:19
* Do not use static certificates for diagnose tests

* Fix operator command tests, move PKI CA creation code into testhelper lib

* Fix compilation error from refactoring
- Avoid this error for now

zlint_test.go:149: got unexpected error from test e_subj_orgunit_in_ca_cert: map[details:The OU attribute in the Subject is prohibited in Root and TLS CA certificates result:error]
- Get better test failure error messages by not shadowing the errors
   when we are attempting to start the MSSQL docker container, so
   we can fail the tests with the proper error message that is occuring
   instead of mssqlhelper.go:60: Could not start docker MSSQL: %!s(<nil>)
…8472)

* Add a core test logger to help capture the MSSQL container output

 - I believe the if t.Failed prevents the logging of the container
   logging as when executed the test isn't considered failed yet.
 - Use a test core logger so that we can capture the container output
   all the time and get it from the captured log files when the test
   fails

* bump image tag to 2022-latest

---------

Co-authored-by: JM Faircloth <jmfaircloth@hashicorp.com>
@tvoran tvoran changed the title ci: update actions/cache v4.0.2 -> v4.2.0 [1.16] ci: update actions/cache v4.0.2 -> v4.2.0 Mar 25, 2025
@tvoran tvoran requested a review from ryancragun March 25, 2025 21:50
@tvoran
Copy link
Copy Markdown
Member Author

tvoran commented Apr 4, 2025

No longer needed.

@tvoran tvoran closed this Apr 4, 2025
@tvoran tvoran deleted the docs/update-1.16-cache-action branch April 4, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants