-
Notifications
You must be signed in to change notification settings - Fork 51
add and implement option to not generate appwrapper in a Cluster #295
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 and implement option to not generate appwrapper in a Cluster #295
Conversation
Co-authored-by: Michael Clifford <[email protected]>
src/codeflare_sdk/cluster/cluster.py
Outdated
@@ -137,6 +144,9 @@ def down(self): | |||
associated with the cluster. | |||
""" | |||
namespace = self.config.namespace | |||
if self.app_wrapper_yaml is None: | |||
self.app_wrapper_yaml = self.create_app_wrapper() |
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 another way to get self.app_wrapper_name
here other than generating the appwrapper yaml. Seems unnecessary to generate the appwrapper yaml just to delete the resource.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MichaelClifford The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issue link
Closes #278
What changes have been made
Changed Cluster definition so it optionally doesn't create an appwrapper. Changed
Cluster.from_k8_cluster_object
so it doesn't create an appwrapper. So whenget_cluster
is called, no appwrapper is generatedVerification steps
Use
get_cluster
and it won't generate an appwrapper. Use Cluster object normally and it will.Checks