-
Notifications
You must be signed in to change notification settings - Fork 38
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
interactive-execution: backend independent #193
interactive-execution: backend independent #193
Conversation
16ca4c5
to
4f52f5a
Compare
77d47d3
to
4d50bbb
Compare
4d50bbb
to
ea66467
Compare
ea66467
to
0a99e80
Compare
0a99e80
to
b6d3224
Compare
c5e7b9e
to
f5511f4
Compare
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.
LGTM
@@ -135,6 +140,7 @@ def _workflow_engine_command(self): | |||
['command'].format( | |||
id=self.workflow.id_, | |||
workspace=self.workflow.get_workspace(), | |||
|
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.
Is there need for this blank line?
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.
Nope, thanks!
f5511f4
to
8180da3
Compare
* Interactive session backend indepdendent set up. * Refactors the way interactive Kubernetes deployment objects are built, from template file (error prone) to native Kubernetes library wrapped with a builder pattern.
* Interactive sessions were leaving hanging Kubernetes objects when some of them could not be created. Let say that the following needed to be created in order: Ingress, Service and Deployment. When the creation of Service failed, hanging Ingresses were left behind as well as marked in DB as successfully deployed.
8180da3
to
0ffb1a8
Compare
Closes reanahub/reana-client#258.