- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Minor
 - 
    None
 
Hi,
We currently have an issue with our JCasc code for the mac plugin. It has always been working but out of the blue it stopped applying the settings. Some context.
We run Jenkins in our Kubernetes cluster on AWS, with the official Helm chart. The Kubernetes cloud in Jenkins has been added by configuring the `jenkins.JCasC.configScripts` key. There I have the following configuration:
```
mac-cloud: |
          jenkins:
            clouds:
            - mac:
                connector:
                  jnlp:
                    jenkinsUrl: 'https://jenkins.internal.mobilevikings.be/'
                    webSocket: false
                idleMinutes: 30
                name: mac
                macHosts:
                - agentConnectionTimeout: 15
                  connectionTimeout: 15
                  credentialsId: 'XXXXX'
                  disabled: false
                  envVars:
                  - key: 'Path'
                    value: '/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin'
                  - key: 'LANG'
                    value: 'en_US.UTF-8'
                  - key: 'LC_ALL'
                    value: 'en_US.UTF-8'
                  - key: 'JAVA_HOME'
                    value: '/var/tools/jdk-13.0.2.jdk/Contents/Home'
                  - key: 'GEM_HOME'
                    value: '$HOME/.gem'
                  - key: 'ANDROID_SDK_ROOT'
                    value: '/var/tools/android-sdk'
                  errorDuration: 300
                  host: 'XXX.XXX.XXX.XXX'
                  key: 'ssh-ed25519 xxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
                  labelString: 'one two three'
                  maxTries: 5
                  maxUsers: 10
                  port: 22
                  readTimeout: 60
                  uploadKeychain: false
                  userManagementTool: 'dscl'
```
So, this config has been working all along but all of a sudden it won't apply anymore and we have no clue what is happening.
When we manually configure this host in the Jenkins interface, it works as expected.
If any more details are needed, please ask and I'll provide them!
Kind regards