Bug report
SecretsProviders can no longer be loaded from nextflow plugins
In 23.10, running Nextflow with a plugin which contains a custom SecretsProvider would be able to use the provider from the plugin. Since 24.04, the LocalSecretsProvider is always used, even if a plugin provides a custom implementation with a higher @Priority.
This seems to be because SecretsLoader.secretContext() is called by the ConfigBuilder during reading of the nextflow config. This happens before plugins have been loaded, so it will only find the LocalSecretsProvider and not any providers from the plugin(s).
Bug report
SecretsProviders can no longer be loaded from nextflow pluginsIn 23.10, running Nextflow with a plugin which contains a custom
SecretsProviderwould be able to use the provider from the plugin. Since 24.04, theLocalSecretsProvideris always used, even if a plugin provides a custom implementation with a higher@Priority.This seems to be because
SecretsLoader.secretContext()is called by theConfigBuilderduring reading of the nextflow config. This happens before plugins have been loaded, so it will only find theLocalSecretsProviderand not any providers from the plugin(s).