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(s3): Refactor S3 config to support separate plugin binaries bucket #715

Merged
merged 2 commits into from
Feb 20, 2020

Conversation

robzienert
Copy link
Member

I forgot that we need to support configuring plugin binaries to go to a different bucket. The normal S3 bucket is typically versioned, whereas the plugin binaries bucket should not be. This refactor keeps all existing S3 configuration the same, but adds all new config for the plugin storage.

@robzienert robzienert requested a review from a team February 19, 2020 21:45
@@ -98,6 +98,7 @@ private synchronized void storeCache(String key, byte[] binary) {
Path binaryPath = CACHE_PATH.resolve(key);
if (!binaryPath.toFile().exists()) {
try {
Files.createDirectories(binaryPath.getParent());
Copy link
Member Author

Choose a reason for hiding this comment

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

Also squeezing in a wee little bug fix if the cache directory doesn't exist. 🙃

@robzienert robzienert merged commit 5749544 into spinnaker:master Feb 20, 2020
@robzienert robzienert deleted the refactor-s3-config branch February 20, 2020 22:37
@plumpy
Copy link
Member

plumpy commented Feb 21, 2020

No code reviews? We have a policy about that, you know...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants