cloudcache.enabled does not properly enable/disable usage of the nf-cloudcache plugin

Bug report

• When explicitly including nf-cloudcache as a plugin in nextflow config, setting cloudcache.enabled = false does not fully disable the plugin from executing

Expected behavior and actual behavior

• Expected behavior - setting the config option to false should fully disable plugin functionality.
• Actual behavior - right now, it's sort of "half disabled"
  • This piece is fully disabled:
    https://github.com/nextflow-io/nextflow/blob/22214c5aba6320dd804412b542d26147a7caa38e/modules/nextflow/src/main/groovy/nextflow/Session.groovy#L435-L437
  • But this piece is not and will end up executed:
    https://github.com/nextflow-io/nextflow/blob/22214c5aba6320dd804412b542d26147a7caa38e/plugins/nf-cloudcache/src/main/nextflow/cache/CloudCacheFactory.groovy#L38-L43

Steps to reproduce the problem

main.nf

workflow {
    main:
    printf "Hello, World!"
}

nextflow.config

plugins {
    id 'nf-cloudcache@0.6.0'
}

cloudcache.enabled = false

Program output

NXF_VER=26.07.0-edge nextflow run .

 N E X T F L O W   ~  version 26.07.0-edge

Launching `./main.nf` [voluminous_agnesi] revision: f70214ed90

ERROR ~ Cloud-cache path not defined - use either -with-cloudcache run option or NXF_CLOUDCACHE_PATH environment variable

 -- Check '.nextflow.log' file for details

Environment

• Nextflow version: 25.10.7, 26.04.6, 26.07.0-edge, syntax parser v1 and v2
• Java version: openjdk version "21.0.11" 2026-04-21 LTS
• Operating system: macOS, linux
• Bash version: zsh 5.9 (arm64-apple-darwin24.0)

Additional context

• We are specifically including the plugin definition to pin the version for the sake of reproducibility

Start with the linked sections of modules/nextflow/src/main/groovy/nextflow/Session.groovy and plugins/nf-cloudcache/src/main/nextflow/cache/CloudCacheFactory.groovy. Run the supplied main.nf and nextflow.config reproduction with nf-cloudcache explicitly pinned and cloudcache.enabled=false. Done means the plugin does not execute and the workflow runs without the cloud-cache path error.