the feature you request is not provided by the config-file-provider, but by the 'pipeline maven' plugin: https://plugins.jenkins.io/pipeline-maven
beside this, I don't think this does make a lot of sense: If you expect this to be configured on each of the pipeline jobs, then you can also just do it inside the Jenkinsfile:

    withMaven(mavenSettingsConfig: 'DEFAULT_MAVEN_SETTINGS', options: [artifactsPublisher(disabled: true)]) {
        sh "mvn install"
    }

Yes, I can use withMaven(mavenSettingsConfig:'...', globalMavenSettingsConfig: '...' but there are two problems:

1. mavenSettingsConfig and globalMavenSettingsConfig use Config File ids, which is hard to maintain
2. The most important thing is that makes the Jenkinsfile binds to a specific Jenkins configuration, which cannot be run everywhere.

Thanks chanjarster for using the Pipeline Maven Integration. Your desire to rely on maven settings defined outside of the pipeline itself is definitively our best practice.
So far, We have just considered to redefine default Maven (global) settings at the folder level (precisely at the AbstractFolder level) (here.

If the config files can be redefined at the Pipeline (ie Item) level, then it would make sense to be able to define the Maven default settings at this level as well.

A technical challenge I see supporting redefinition of default (global) Maven settings at the Pipeline level is that we would probably have to write a dedicated config screen. At the moment, our configuration block is a fragment intended to be included in the folder configuration file.

cleclerc I see, thanks