Skip to content

[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

Merged
merged 5 commits into from
Mar 8, 2023

Conversation

easyCZ
Copy link
Member

@easyCZ easyCZ commented Mar 8, 2023

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:

  • Installer doesn't know about blobserve implementation details (from packaging perspective)
  • Installer builds faster

Related Issue(s)

Fixes #

How to test

CI passes

Release Notes

NONE

Documentation

Build Options:

  • /werft with-github-actions
    Experimental feature to run the build with GitHub Actions (and not in Werft).
  • leeway-no-cache
    leeway-target=components:all
  • /werft no-test
    Run Leeway with --dont-test
Publish Options
  • /werft publish-to-npm
  • /werft publish-to-jb-marketplace
Installer Options
  • with-ee-license
  • with-dedicated-emulation
  • with-ws-manager-mk2
  • workspace-feature-flags
    Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-gce-vm
    If enabled this will create the environment on GCE infra
  • /werft with-integration-tests=all
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

@@ -44,40 +44,6 @@ type BlobserveInlineVars struct {
SupervisorImage string `json:"supervisor"`
}

type BlobSpace struct {
Copy link
Member Author

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

@easyCZ easyCZ force-pushed the mp/blobserve-cfg branch from f260b8f to cb3b460 Compare March 8, 2023 10:29
@easyCZ easyCZ mentioned this pull request Mar 8, 2023
14 tasks
@akosyakov
Copy link
Member

akosyakov commented Mar 8, 2023

I wonder should not we separate implementation from api via dedicated component like components/blobserve-api. I think we follow this pattern in all other components, but overlooked here because of historical reasons. It would separate cleanly go modules?

Copy link
Member

@akosyakov akosyakov left a 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

@easyCZ
Copy link
Member Author

easyCZ commented Mar 8, 2023

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

@easyCZ
Copy link
Member Author

easyCZ commented Mar 8, 2023

/unhold

@roboquat roboquat merged commit 385a323 into main Mar 8, 2023
@roboquat roboquat deleted the mp/blobserve-cfg branch March 8, 2023 21:23
@roboquat roboquat added deployed: IDE IDE change is running in production deployed Change is completely running in production labels Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: IDE IDE change is running in production deployed Change is completely running in production release-note-none size/L team: IDE
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants