Thanks, looks good!

We just need to ensure the consistency of pinned_versions.yaml and the following locations:

swell/src/swell/deployment/platforms/nccs_discover_sles15/task_questions.yaml

Lines 10 to 14 in 597bbbe

	existing_jedi_build_directory:
	default_value: /discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15/build-intel-release
	existing_jedi_source_directory:
	default_value: /discover/nobackup/projects/gmao/advda/swell/JediBundles/fv3_soca_SLES15

I modified the platform task_question.yaml files to point to pinned version jedi bundles for SLES12 and SLES15.

Also, if we do that, is there a way to enforce a particular set of options at runtime? I.e., When you go to set self.config.jedi_build_method, if it's set to something invalid, it'll fail immediately? Not sure if the string-drop-list or some other type will do that for us. In any case, if there's a way to easily do that, we should do it, because that will allow us to remove lots of if self.config.jedi_build_method() in (...) code blocks.

In task_questions.yaml, I modified jedi_bundle_method to include the new valid options, and then I changed it to string-drop-list which works well for constraining the user to only valid build methods. If there are any remaining if self.config.jedi_build_method() in (...) code blocks, it's because the task itself is checking for specific build methods and aborts if other valid methods were provided. For example, BuildJediByLinking aborts if the user has selected either the create or pinned_create build method.