Skip to content

Backport of ci: ensure int test docker pull goes through proxy into release/1.20.x#21824

Merged
zalimeni merged 1 commit into
release/1.20.xfrom
backport/zalimeni/fix-docker-pull-int-test/apparently-proper-mudfish
Oct 14, 2024
Merged

Backport of ci: ensure int test docker pull goes through proxy into release/1.20.x#21824
zalimeni merged 1 commit into
release/1.20.xfrom
backport/zalimeni/fix-docker-pull-int-test/apparently-proper-mudfish

Conversation

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #21819 to be assessed for backporting due to the inclusion of the label backport/1.20.

The below text is copied from the body of the original PR.


So we don't get rate limited.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/zalimeni/fix-docker-pull-int-test/apparently-proper-mudfish branch from a6954ef to 5129110 Compare October 14, 2024 19:03
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@github-actions github-actions Bot added type/ci Relating to continuous integration (CI) tooling for testing or releases theme/contributing Additions and enhancements to community contributing materials labels Oct 14, 2024
@zalimeni zalimeni merged commit 461050d into release/1.20.x Oct 14, 2024
@zalimeni zalimeni deleted the backport/zalimeni/fix-docker-pull-int-test/apparently-proper-mudfish branch October 14, 2024 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants