-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[installer] Do not pull blobserve implementation into installer #16729
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
Conversation
@@ -44,40 +44,6 @@ type BlobserveInlineVars struct { | |||
SupervisorImage string `json:"supervisor"` | |||
} | |||
|
|||
type BlobSpace struct { |
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.
This is moved to the config
package
I wonder should not we separate implementation from api via dedicated component like |
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.
I think it makes sense, looks like a tech debt.
Not sure whether we should rather separate it on level of leeway components instead as we do for other components.
/hold
if you decide to refactor it once more
Given the necessary dependencies are already not included with this change, I don't think we necessarily need to introduce the api package for this. In some cases it could make sense, but here it'd just hold the config which seems unnecessary |
/unhold |
Description
By referencing the
blobserve/pkg/blobserve
, we were effectively pulling all of blobserve (and it's dependencies) directly as a dependency into the installer.This change moves the necessary config into the
blobserve/config
such that we only depend on that, and not on the blobserve implementation packages (see removed deps in installer).This in turn does the following:
Related Issue(s)
Fixes #
How to test
CI passes
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-test
Publish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh