We added the ability to use secrets in the includeConfig path in #4840 . This works for local secrets, but not AWS secrets, because AWS secrets requires the xpack-amzn plugin and the config is resolved before plugins are loaded, since the config may include additional plugins.
To fix this I think we would need to load plugins in two phases, adding an "early" phase which happens before the config is resolved.
Not sure how much demand there is for this use case, but it would include any AWS Batch run in Seqera Platform that loads a private config using a secret credential.
We added the ability to use secrets in the
includeConfig
path in #4840 . This works for local secrets, but not AWS secrets, because AWS secrets requires the xpack-amzn plugin and the config is resolved before plugins are loaded, since the config may include additional plugins.To fix this I think we would need to load plugins in two phases, adding an "early" phase which happens before the config is resolved.
Not sure how much demand there is for this use case, but it would include any AWS Batch run in Seqera Platform that loads a private config using a secret credential.
cc @markpanganiban