Currently (by inspection) this plugin reads the secrets file during configuration, which will result in a configuration cache miss when the contents of the secrets file changes
Could we use the lazy APIs (e.g. fileContents so this file is not read during configuration and therefore doesn't need to be a configuration cache input?
Currently (by inspection) this plugin reads the secrets file during configuration, which will result in a configuration cache miss when the contents of the secrets file changes
Could we use the lazy APIs (e.g. fileContents so this file is not read during configuration and therefore doesn't need to be a configuration cache input?