Working on a customers golden image machines, when creating a new RHEL 7 server going through the analysis process is causing the /etc/yum/pluginconf.d/subscription-manager.conf file to be replaced by a new file. The playbook is being reported by the customer to be creating a new temporary file and replacing the old one with it.

The customer is reporting this behaviour is caused by the following play in the analysis role:
```

• name: analysis-leapp | Register to leapp activation key
  community.general.redhat_subscription:
  state: present
  activationkey: "{{ satellite_activation_key_leapp }}"
  org_id: "{{ satellite_organization }}"
  force_register: true
  notify: Register to pre leapp activation key
  when:
• leapp_upgrade_type == 'satellite'
• satellite_organization is defined
• satellite_activation_key_leapp is defined
  ```

The content of the directory before the analysis:
```
[main]
enabled=1
```

The content of the directory after:
```
[main]
enabled=0
```

In an effort to resolve this, the customer has tried the following:
```

• name: analysis-leapp | Register to leapp activation key
  community.general.redhat_subscription:
  state: present
  activationkey: "{{ satellite_activation_key_leapp }}"
  org_id: "{{ satellite_organization }}"
  force_register: true
  notify: Register to pre leapp activation key
  when:
• leapp_upgrade_type == 'satellite'
• satellite_organization is defined
• satellite_activation_key_leapp is defined
• sub_identity_raw.stdout != "CUSTOMER_KEY_NAME"
  ```

This has been unsuccessful though as the key name is referred to other plays in various roles being used in the analysis and upgrade process, so would mean editing more roles and deviating more from the provided roles, which may cause some issues over longer periods of time. Advice on how to work to a solution would be very much appreciated.