VOTE-967: Disable disable_language module for non production environments.

[daniel-crowder]

Jira ticket

VOTE-967

Description

Update configurations to enable disable_language module only on production and local environments.

• Additional changes include using partial configurations for user roles and system performance.

Deployment and testing

Pre-deploy

N/A

Post-deploy

1. Locally run lando retune.

QA/Test

1. Locate your /web/sites/settings.local.php file and open.
2. Find the following line within:
   $config['config_split.config_split.local']['status'] = TRUE;
3. Use this line of code to switch between environments which will dictate the environment-based config that will be imported with lando drush cim is executed.

Local Environment Testing:

1. Set $config['config_split.config_split.local']['status'] = TRUE;
2. Run lando drush cim
3. Login to the site and confirm

• Disable Language Module is enabled (/admin/config/regional/language/disable_language)

Non Production Testing:

1. Set $config['config_split.config_split.non_production']['status'] = TRUE;
2. Run lando drush cim
3. Login to the site and confirm

• Disable Language Module is disabled (/admin/modules)
• CSS & JS aggregation is enabled (/admin/config/development/performance)

Production Testing:

1. Set $config['config_split.config_split.production']['status'] = TRUE;
2. Run lando drush cim
3. Login to the site and confirm

• Disable Language Module is enabled (/admin/config/regional/language/disable_language)
• Confirm that Amharic and Hmong languages are disabled (/admin/config/regional/language)
• CSS & JS aggregation is enabled (/admin/config/development/performance)

Checklist for the Developer

• A link to the JIRA ticket has been included above.
• No merge conflicts exist with the target branch.
• Automated tests have passed on this PR.
• A reviewer has been designated.
• Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

• The file changes are relevant to the task objective.
• Code is readable and includes appropriate commenting.
• Code standards and best practices are followed.
• QA/Test steps were successfully completed, if applicable.
• Applicable logs are free of errors.