Skip to content
This repository has been archived by the owner on Jan 28, 2022. It is now read-only.

Adding support for using existing_cluster_name as well as existing_cluster_id #86

Closed
Azadehkhojandi opened this issue Oct 17, 2019 · 0 comments · Fixed by #126
Closed

Adding support for using existing_cluster_name as well as existing_cluster_id #86

Azadehkhojandi opened this issue Oct 17, 2019 · 0 comments · Fixed by #126
Assignees
@Azadehkhojandi
Labels
enhancement New feature or request high-priority

Comments

@Azadehkhojandi
Copy link
Contributor

Currently Running a job on an existing cluster requires a cluster_id, add an option that users can provide the k8s object name of the cluster
@Azadehkhojandi Azadehkhojandi added the enhancement New feature or request label Oct 17, 2019
@Azadehkhojandi Azadehkhojandi self-assigned this Nov 26, 2019
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
dae4111 
…uster_id Azure#86
@Azadehkhojandi Azadehkhojandi mentioned this issue Nov 28, 2019
Merged
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
57ea9c8 
…uster_id Azure#86
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
9058d9a 
…uster_id Azure#86
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
ca70b12 
…uster_id Azure#86
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
c358c49 
…uster_id Azure#86
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
cb8f530 
…uster_id Azure#86
Azadehkhojandi added a commit to Azadehkhojandi/azure-databricks-operator that referenced this issue Nov 28, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name as well as existing_cl…
a0f7f78 
…uster_id Azure#86
Azadehkhojandi added a commit that referenced this issue Dec 1, 2019
@Azadehkhojandi
Adding support for using existing_cluster_name (#126)
8a81450 
* Adding support for using existing_cluster_name as well as existing_cluster_id #86

* add new tests and clean up tests
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Azadehkhojandi Azadehkhojandi

Labels
enhancement New feature or request high-priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adding support for using existing_cluster_name Azadehkhojandi/azure-databricks-operator
2 participants
@Azadehkhojandi @idc101