Update wrapped MET config files to reference MET_TMP_DIR in tmp value

[georgemccabe]

The default value is currently /tmp, however some machines discourage using this directory to write temp files. When running through METplus wrappers, the environment variable MET_TMP_DIR is set which overrides this value. Running with the wrapped MET config files outside of the wrappers (via command line) require the other environment variables to be set to run or it will fail. If all of the env vars set for a command are set, then it will include MET_TMP_DIR, however this may not always be the case. Setting the value for tmp to $(MET_TMP_DIR) will ensure that the value is overridden properly when running by hand and make it clear to users that the value set for tmp in those files is not being used.

Describe the Enhancement

Change the files in parm/met_config to reference the MET_TMP_DIR environment variable instead of /tmp.

Time Estimate

~< 1 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

4.1.0

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.