Disable the SMUS generative AI extension in SMAI and disable jupyter-… #762
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.
…ai extension in SMUS
Description
SMUS will support a single generative AI chat experience provided by sagemaker_gen_ai_jupyterlab_extension. to accomplish this in SMUS spaces, jupyter-ai will be disabled.
In SMAI, jupyter-ai will be the single generative AI chat experience, so the sagemaker_gen_ai_jupyterlab_extension will be disabled in SMAI spaces.
Testing Done
Manually disabled the extensions using the commands included in start-jupyter-server and start-sagemaker-ui-jupyter-server and confirmed only one chat experience exists after running command.
Description
See above
Type of Change
Release Information
Does this change need to be included in patch version releases? By default, any pull requests will only be added to the next SMD image minor version release once they are merged in template folder. Only critical bug fix or security update should be applied to new patch versions of existed image minor versions.
If yes, please explain why:
How Has This Been Tested?
Manually disabled the extensions using the commands included in start-jupyter-server and start-sagemaker-ui-jupyter-server and confirmed only one chat experience exists after running command.
Checklist:
Test Screenshots (if applicable):
Related Issues
[Link any related issues here]
Additional Notes
[Any additional information that might be helpful for reviewers]