-
Notifications
You must be signed in to change notification settings - Fork 527
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
Allow GCS config for setting attributes on new objects #1368
Conversation
Looks like I was wrong about the default yaml unmarshaling tags for the upstream config object, perhaps because the underlying type is an interface. I think we'll probably want to build a config for the features we plan to support. Thought, using the default lowercase name for the yaml field does seem to work. This would be simpler than translating between the objects. Integration tests will soon tell us something. |
96c1d91
to
dc2af8a
Compare
880f6de
to
9d33c11
Compare
9d33c11
to
c0f2ee6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good! a few final things to clean up. also can you regenerate the config in manifest.md?
137b9d0
to
fc18c68
Compare
What this PR does:
Here we add two options to configure GCS object attributes. One to control the aspects of object caching, and the other to allow users to specify metadata on the object.
Which issue(s) this PR fixes:
Fixes #1348
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]