BGD-6242 - Workspace stuck in starting due to missing volume - release bigdata-proxy 0.5.7 #256
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HafdisE
force-pushed
the
BGD-6242-Workspace-stuck-in-starting-due-to-missing-volume-2
branch
from
973feed to
d3ff80c
Compare
alextarasov-spot
approved these changes
Dec 12, 2024
HafdisE
deleted the
BGD-6242-Workspace-stuck-in-starting-due-to-missing-volume-2
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Jira ticket
https://spotinst.atlassian.net/browse/BGD-6242
Description
Update of bigdata-proxy that supports the new configuration option (storage class name)
Demo
N/A
Checklist
How to test
See this PR for more details: https://github.com/spotinst/bigdata-proxy/pull/70
Test plan and results