Centralize JCB variable lists#2171
Draft
DavidNew-NOAA wants to merge 14 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR centralizes lists of variables, as well as "field IO names", from various jcb-gdas model and algorithm templates into jcb-base.yaml.j2.
I'm leaving this untested PR as draft for now to get feedback. I want to make sure that the substitutions of these variables lists makes sense, but also that this doesn't overly complicate jcb-base.yaml.j2.
Companion PRs
N/A
Issues
N/A
Automated CI tests to run in Global Workflow