Skip to content

chore(devservices): Remove all old sentry devservices code #92512

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

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

hubertdeng123
Copy link
Member

Now that devservices toggle is in, we should be safe to remove this code

https://linear.app/getsentry/issue/DI-560/completely-remove-code-related-to-sentry-devservices

@hubertdeng123 hubertdeng123 requested review from a team as code owners May 29, 2025 20:59
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 29, 2025


@contextlib.contextmanager
def get_docker_client() -> Generator[docker.DockerClient]:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there's a few imports you'll have to address too

[email protected] ~/d/sentry master $ rg -S 'devservices import'                                                                                      0
bin/split-silo-database
8:from sentry.runner.commands.devservices import get_docker_client

src/sentry/testutils/pytest/relay.py
14:from sentry.runner.commands.devservices import get_docker_client

src/sentry/runner/commands/devserver.py
12:from sentry.runner.commands.devservices import get_docker_client

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I noticed thought this might be a bit easier to do

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

going to punt this until next week or so for now

@hubertdeng123 hubertdeng123 marked this pull request as draft May 29, 2025 21:40
except docker.errors.DockerException:
if DARWIN:
if USE_COLIMA:
click.echo("Attempting to start colima...")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the expectation before was that devservices would automatically try and start colima if it couldn't connect to a docker daemon

now it's this (and you can't even use --help):

[email protected] ~/d/sentry master $ .venv/bin/devservices up                                                                                      127
Unable to connect to the docker daemon. Is the docker daemon running?
[email protected] ~/d/sentry master $ .venv/bin/devservices --help                                                                                    1
Unable to connect to the docker daemon. Is the docker daemon running?

before we remove all this (long awaited!) can we at least get devservices to do this on macos?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants