One approach to doing this could be to put the installation of the jupyter extensions and maap-py in the entrypoint.sh instead of our environment.yml and read the version number from setting the environment variable our devfiles ie pip install maap_libs_extension=${EXTENSION_VERSION}. With this approach, users would get updated UI features from the extensions when they restart their workspace instead of needing to create a new workspace with the latest release. Exact version would be specified in the devfiles, not just the latest tag
Discussion points:
Marjorie and Grace are unsure how much this would aid development testing
Would this make users less likely to update their workspace to the newest version because are they sometimes doing it for UI changes? If a lot of the other changes are behind the scenes they might not want to update for those changes
Would need to make sure the users who are on older workspace versions (but “older workspace versions” would still be 4.1+ depending on when we implement this) still have compatibility with the new UI extensions/ maap-py versions
Discussed in 9/12 sprint planning meeting
One approach to doing this could be to put the installation of the jupyter extensions and maap-py in the entrypoint.sh instead of our environment.yml and read the version number from setting the environment variable our devfiles ie
pip install maap_libs_extension=${EXTENSION_VERSION}
. With this approach, users would get updated UI features from the extensions when they restart their workspace instead of needing to create a new workspace with the latest release. Exact version would be specified in the devfiles, not just the latest tagDiscussion points: