Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: allow s3 cache access for the "docker" runner executor #817

Merged

Conversation

ryancausey
Copy link
Contributor

Closes #816

Description

This fixes the "docker" runner executor not having access to the S3 bucket by always attaching the bucket policy if it exists.

Migrations required

NO

Verification

Ran changes locally and observed the issue was resolved with this change.

@github-actions
Copy link
Contributor

Hey @ryancausey! 👋

Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

  • the problem being solved
  • the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE.

The following ChatOps commands are supported:

  • /help: notifies a maintainer to help you out

Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command.

This message was generated automatically. You are welcome to improve it.

@kayman-mk
Copy link
Collaborator

Yes, we shouldn't exclude the docker executor here.

Copy link
Collaborator

@kayman-mk kayman-mk left a comment

Choose a reason for hiding this comment

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

Thanks for the quick fix you provided.

@kayman-mk kayman-mk merged commit a17015f into cattle-ops:main Apr 27, 2023
kayman-mk pushed a commit that referenced this pull request Apr 27, 2023
🤖 I have created a release *beep* *boop*
---


##
[6.3.1](6.3.0...6.3.1)
(2023-04-27)


### Bug Fixes

* allow s3 cache access for the "docker" runner executor
([#817](#817))
([a17015f](a17015f))
* remove explicit aws_s3_bucket_acl
([#815](#815))
([5d88370](5d88370))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Signed-off-by: Niek Palm <[email protected]>
Co-authored-by: cattle-ops-releaser[bot] <126345536+cattle-ops-releaser[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@ryancausey ryancausey deleted the fix/allow-s3-access-with-docker-executor branch December 14, 2023 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

403 forbidden error when using cache with the "docker" runners executor
2 participants