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

#174: Added get_language_definition to the language container deployer #175

Merged
merged 4 commits into from
Jan 5, 2024

Conversation

tkilias
Copy link
Collaborator

@tkilias tkilias commented Jan 5, 2024

Fixes #174

All Submissions:

  • Is the title of the Pull Request correct?
  • Is the title of the corresponding issue correct?
  • Have you updated the changelog?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Are you mentioning the issue which this PullRequest fixes ("Fixes...")
  • Before you merge don't forget to run tests in AWS CodeBuild, by adding [CodeBuild] to the commit message

@tkilias tkilias changed the title Added get_language_definition to the language container deployer #174: Added get_language_definition to the language container deployer Jan 5, 2024
@@ -213,6 +213,16 @@ def _update_previous_language_settings(self, alter_type: LanguageActivationLevel
path_in_udf, prev_lang_aliases)
return new_definitions_str

def get_language_definition(self, bucket_file_path: str):
Copy link
Collaborator

Choose a reason for hiding this comment

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

would it be cleaner to split _generate_new_language_settings into a function which generates the " other_definitions" and one which generates "new_language_alias_definition"? then we do not have to call with an empty list, but instead have one calling function calling both, and one only calling one?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

in general yes, but because we haven't extracted this code into a central place, yet, we need to manually copy changes to sagemaker-extension, for that reason, I would like to keep the changes simple for the moment

Copy link
Collaborator

Choose a reason for hiding this comment

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

alright. maybe add a comment or something to do later?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

will create a ticket

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@tkilias tkilias merged commit b80e199 into main Jan 5, 2024
4 checks passed
@tkilias tkilias deleted the feature/174_add_get_language_definition branch January 5, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add get_language_definition to the language container deployer
2 participants