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
Description
Many things are templated in parm/config/config.base.emc.dyn but HPSS_PROJECT is not. Not all users are able to write to emc-global, this should be configurable like how ACCOUNT is.
Requirements
Have HPSS_PROJECT filled in by setup_expt.py
Acceptance Criteria (Definition of Done)
When the requirement is met
(Optional): Suggest A Solution
change to a template in parm/config/config.base.emc.dyn
modify workflow/setup_expt.py as appropriate to make the default emc-global but accept optional values if specified.
The text was updated successfully, but these errors were encountered:
@aerorahul@WalterKolczynski-NOAA I didn't test this yet, perhaps this issue is moot and can be already done with the existing infrastructure put in place recently to overwrite defaults. Just wanted to capture it in an issue just in case work was needed to make this work.
Update: looks like ACCOUNT doesn't even work by modifying config.base through a YAML file... I think it is because @ACCOUNT@ is already replaced by fv3-cpu before the script even reads the YAMLs.
Description
Many things are templated in
parm/config/config.base.emc.dyn
butHPSS_PROJECT
is not. Not all users are able to write to emc-global, this should be configurable like howACCOUNT
is.Requirements
Have
HPSS_PROJECT
filled in bysetup_expt.py
Acceptance Criteria (Definition of Done)
When the requirement is met
(Optional): Suggest A Solution
parm/config/config.base.emc.dyn
workflow/setup_expt.py
as appropriate to make the defaultemc-global
but accept optional values if specified.The text was updated successfully, but these errors were encountered: