Prevent bucket creation when workspace doesn't need remote storage support #4989
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.
We have some workloads that don't require the use remote storage because we never create a backup or snapshot of their content, namely:
image-build
andghost
.This PR introduces a flag on ws-daemon's
InitWorkspace
call namedRemoteStorageDisabled
which, when set to true, does not callEnsureExists
on the remote storage. If on such a workspace a remote storage operation is attempted (e.g.TakeSnapshot
) orDisposeWorkspace(backup: true)
) such a call will fail withFailedPrecondition
.This also prevents name clashes due to globally unique bucket names in GCP and S3, and image-builder currently using a fixed owner for all image builds.
fixes #4929