fix: update bucket creation to set project as bucket.project
#1912
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creation of a bucket is modifying which field is used to specify the project a bucket is associated with. Changing from
parent
tobucket.project
. This change updates our handling to use this new field.The existing
parent
is set to the sentinel valueprojects/_
which was previously only implicitly found in the bucket name.Update testbench tag to v0.35.0 which includes the new field behavior.
ApiaryConversions have been updated to track the project attribute when cross converting as the property
.x_project
; this value should avoid any possible collision if the field name project is supported in the future while the client is operating in this intervening time. If/when StorageObject receives its own project field we should switch to using it.Fix associated with b/254678990
This PR is a preemptive fix for the change which will rollout to fix http://b/254678990