Re-add init_scripts to ClusterService.create_cluster#351
Closed
sd2k wants to merge 1 commit intodatabricks:mainfrom
Closed
Re-add init_scripts to ClusterService.create_cluster#351sd2k wants to merge 1 commit intodatabricks:mainfrom
sd2k wants to merge 1 commit intodatabricks:mainfrom
Conversation
This was removed in [this PR][!325] by autogeneration, but the /clusters/create API endpoint should still accept the init_scripts argument, and it's useful for creating clusters programmatically. I'm not sure how autogeneration works so this could happen again in future - perhaps it should be looked into somewhere upstream instead, but for now this would be useful! [!325]: databricks#325 (comment)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It looks like this is being bashed around by the code generation: it was removed in #200, re-added in #266, then removed again by #325.
I'm not sure how the code generation works so this could happen again in future. Perhaps it should be looked into somewhere upstream instead, for now it would be useful to get this merged if possible!
Fixes #264 and #335.