User-defined "pinned versions" for JEDI repos

[asewnath]

Description

Adding ability for an optional pinned version config file to override defaults in jedi_bundle.

Example pinned version config file:

- ufo:
    branch: 64655cf61a9d22c88c0f20e740554ca5225790bc 
    commit: True

New config field commit is introduced to specify if the given branch is a hash. This follows the yaml configuration style in jedi_bundle's default configs. Note that the pinned version config file can also handle branches and tags.

Pinned version config file is saved in jedi_bundle and can be invoked with these flags:
jedi_bundle --pinned_versions
jedi_bundle -pv

Contents of the pinned versions config file is added to build.yaml. Then, the Clone task proceeds as normal with the build.yaml file.

See issue for more information: GEOS-ESM/swell#345

[asewnath]

TODO add github actions test for pinned version case

[Dooruk]

Hi @asewnath , just saw this but I didn't receive any notifications. Is it ready for testing?

[asewnath]

Hi @asewnath , just saw this but I didn't receive any notifications. Is it ready for testing?

Hi @Dooruk, I haven't added the github action test for this yet but technically it's ready for testing

[ashiklom]

I'm pretty sure import typing is not necessary to enable type hinting, so I recommend removing it (from git.py). The hints are ignored by the runtime anyway, so it doesn't really do anything. I think you mostly import typing for specific functions or classes -- e.g., from typing import Union.

Otherwise, this is good to go. Nice work! This will be a really useful change to making SWELL work more reliably and giving us more control over our integration with JEDI.

[asewnath]

I'm pretty sure import typing is not necessary to enable type hinting, so I recommend removing it (from git.py). The hints are ignored by the runtime anyway, so it doesn't really do anything. I think you mostly import typing for specific functions or classes -- e.g., from typing import Union.

Otherwise, this is good to go. Nice work! This will be a really useful change to making SWELL work more reliably and giving us more control over our integration with JEDI.

Ah okay good to know! I thought import typing was required