Skip to content
This repository was archived by the owner on Jun 3, 2025. It is now read-only.

Enable pushing cache with --no-push#3181

Merged
aaron-prindle merged 1 commit intoGoogleContainerTools:mainfrom
leosunmo:allow-cache-push-with-no-push
Jun 4, 2024
Merged

Enable pushing cache with --no-push#3181
aaron-prindle merged 1 commit intoGoogleContainerTools:mainfrom
leosunmo:allow-cache-push-with-no-push

Conversation

@leosunmo
Copy link
Copy Markdown
Contributor

Make sure we check --no-cache-push instead of --no-push when deciding whether to push cache or not.

Fixes #3180

Description
Allows for pushing to cache even if --no-push is enabled. This is useful in scenarios where you want to benefit (and contribute) to cache but ultimately save the image to a tar file, for example when container scanning in CI pipelines.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes unit tests
  • Adds integration tests if needed.

Reviewer Notes

  • The code flow looks good.
  • Unit tests and or integration tests added.

Release Notes

Enable pushing cache even when --no-push is provided. To disable pushing cache, use --no-push-cache.

Make sure we check --no-cache-push instead of --no-push when deciding whether to
push cache or not.
Copy link
Copy Markdown
Collaborator

@aaron-prindle aaron-prindle left a comment

Choose a reason for hiding this comment

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

Thanks @leosunmo for the fix and explanation here. LGTM

@aaron-prindle aaron-prindle merged commit 6a340c6 into GoogleContainerTools:main Jun 4, 2024
@leosunmo leosunmo deleted the allow-cache-push-with-no-push branch June 5, 2024 20:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support pushing cache even when using --no-push

2 participants