Deprecate auto-installer for Studio Lifecycle Configs #15
Description
With the recent launch of lifecycle configuration scripts for SageMaker Studio, some great news for users is that our old auto-installer solution is pretty much redundant!
Instead, the relevant samples in the sagemaker-studio-lifecycle-config-examples repo should now show domain admins how they can configure automatic (re)-installation of the extension on JupyterServer start-up - including support for SSO-authenticated Studio domains which the old auto-installer solution couldn't handle.
The only potential gaps I can still think of to justify keeping it around would be:
- Are there sufficient docs/examples to help admins make sure the auto-shutdown installer lifecycle config script gets automatically attached to new users as they're created?
- Any other potential non-shutdown-extension-related automation tasks users might be interested to tackle through Jupyter APIs? (but probably outside the scope of this repository)
...Apart from that, I guess best way forward is probably to delete the folder and update the main README with new instructions?