Skip to content
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

Add jupyter builds and interactive sessions events to orchest-api (notifications) #950

Merged

Conversation

fruttasecca
Copy link
Member

@fruttasecca fruttasecca commented May 16, 2022

Description

Adds support for jupyter builds and interactive sessions events to the orchest-api, these events can now be subscribed to and are now part of the analytics module.

@yannickperrenet one point of discussion for me here would be about the conceptual nesting of events, i.e. project:interactive-session:started vs a possible project:pipeline:interactive-session:started. I have currently gone for the former but I have no strong feelings about it (not even mild tbh), would be good to reach a consensus pre-merge to avoid breaking schemas later.

Checklist

  • In case I changed one of the services’ models.py I have performed the appropriate database
    migrations (refer to scripts/migration_manager.sh).

@fruttasecca fruttasecca added improvement An improvement or enhancement to an existing feature. internal Something that does not affect users directly, e.g. code quality. labels May 16, 2022
@fruttasecca fruttasecca changed the title Improv/add builds events to orchest api Add jupyter builds and interactive sessions events to orchest-api May 16, 2022
@fruttasecca fruttasecca changed the title Add jupyter builds and interactive sessions events to orchest-api Add jupyter builds and interactive sessions events to orchest-api (notifications) May 16, 2022
@yannickperrenet
Copy link
Contributor

project:interactive-session:started vs a possible project:pipeline:interactive-session:started

Given that pretty much all session related calls needs a project and pipeline UUID it clearly shows that sessions are a project:pipeline entity. I think it makes most sense to model the events as closely as possible to the current state of things. Thus voting for project:pipeline:interactive-session:started ^_^

events._register_interactive_session_service_restarted(
    project_uuid, pipeline_uuid
)

Copy link
Contributor

@yannickperrenet yannickperrenet left a comment

Choose a reason for hiding this comment

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

LGTM!

@fruttasecca
Copy link
Member Author

Thus voting for project:pipeline:interactive-session:started ^_^

Alright sounds good 👍

@fruttasecca fruttasecca merged commit 00342f7 into improv/orchest-api-analytics May 19, 2022
@fruttasecca fruttasecca deleted the improv/add-builds-events-to-orchest-api branch May 19, 2022 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement An improvement or enhancement to an existing feature. internal Something that does not affect users directly, e.g. code quality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants