You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
My impression is that most contributors will not know or care which tag of the pangeo/forge image we use as a base, so long as it contains their specified version of pangeo_forge_recipes, and any other dependencies they need.
That being said, we will be setting this parameter during recipe parsing an execution, and for certain users (certainly developers) it's a useful option to expose.
So maybe we should deprecate the pangeo_notebook_version field (which as been ignored for some time already) in favor of a more general (optional?) field named something like, image_tag?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My impression is that most contributors will not know or care which tag of the
pangeo/forge
image we use as a base, so long as it contains their specified version ofpangeo_forge_recipes
, and any other dependencies they need.That being said, we will be setting this parameter during recipe parsing an execution, and for certain users (certainly developers) it's a useful option to expose.
So maybe we should deprecate the
pangeo_notebook_version
field (which as been ignored for some time already) in favor of a more general (optional?) field named something like,image_tag
?The text was updated successfully, but these errors were encountered: