Documentation for Cloud Next states to not explicitly set memcache settings but customers still using this package

[janusman]

Documentation for Cloud Next states to not explicitly set memcache settings, can this package make that clear and/or not activate when running within an ACN environment?

[jameswilson]

We just got upgraded from Cloud Professional to Cloud Next on our DEV environment, but TEST PROD appears to still be on a dedicated server (not sure).

Additionally confirmed by SSHing into DEV which produces a hostname like this: @sshd-598d99d797-njkf7 whereas SSHing into PROD shows a hostname @ded-44561.

In acquia/memcache-settings/memcache.settings.php there is a reference to $conf['acquia_hosting_site_info']['db']['name'] . '_'; which is causing a PHP warning variable $conf is undefined on DEV only (no errors on TEST or PROD, despite the same code being used).

To be clear, I've manuall copy/pasted the contents of memcache.settings.php to our settings.php file for our use case, which explains why the line of code depicted in the screenshot above differs from the line of code where this was originally present in the memcache.settings.php file.

I cannot find any mention of acquia_hosting_site_info anywhere else online or the best approach to solve this.

The line of code causing issues on DEV seems to be related to multisite, which this site doesnt use, so I'm leaning towards just commenting out this line of code in my settings.php, but should I do something different instead such as just remove the entire chunk of code i pulled from memcache.settings.php (at the risk of losing memcache configuration on PROD?) Or maybe there is a way to gate the code for only Non-Cloud Next environments?

Please help with a suggested approach! Thank you.