Repository navigation
Investigate adding support for BucketAccessControls: insert #292
Description
This is for discussion.
Do we need to provide support for BucketAccessControls: insert or rather expect users to rely on bucket update/patch?
I think update/patch method should be enough. We can always add BucketAccessControls: insert later if someone requests it.
Activity
Remove storage todos (replaced with issues: googleapis#288 googleapis…
aozarov commentedon Oct 29, 2015
I agree and I think we should either close it (and re-open per request) or label it as "enhancement" which
is not likely to be implemented.
mziccard commentedon Oct 29, 2015
I'm closing this. We can reopen in the future if users request this feature or we feel like it should be added.
chore(java): enable generated-files-bot (googleapis#292)
chore: remove All rights reserved clause from java.header (#1148) (#292)
build(deps): update dependency com.google.cloud:google-cloud-shared-c…
build(deps): update dependency com.google.cloud:google-cloud-shared-c…
chore(main): release 2.3.3 (#292)
chore(main): release 1.2.5 (#292)
chore(main): release 2.3.5 (#301)
chore(deps): update dependency com.google.cloud:google-cloud-dms to v…
deps: update dependency com.google.cloud:google-cloud-shared-dependen…
chore(main): release 1.2.5 (#289)
chore(main): release 1.2.8 (#298)
chore(main): release 2.4.4 (#310)
chore(main): release 2.0.0 (#739)
chore: release 0.119.5 (#292)
chore: regenerate README (#292)
Refactor shared IAM-based signing (#292)
Refactor shared IAM-based signing (#292)
chore: regenerate README (googleapis#292)
build(java): use code-suggester v1 tag rather than full semver (#292)
build(java): use code-suggester v1 tag rather than full semver (#292)
fix: if a flow control setting is not provided use zero (#292)
fix: if a flow control setting is not provided use zero (#292)