[5.x]: Cannot use env vars for plugin licenses

[harry2909]

What happened?

Description

When trying to store env variables in the plugin licenses, craft seems to just revert them back to the plain text value whenever we run project config apply.

Happy to send a video over to an email for evidence, though this has been reported internally as being really sporadic.

Update:
I have actually just noticed, it looks like something is writing to my .env file? If I use $license as the env var in the CMS, it then adds that env var to the file. Though I would've thought if the env var already exists and the license key is set to use it in the project config, it wouldn't matter.

Steps to reproduce

1. Save an env variable in a plugin license
2. Craft shows that there are pending project config changes
3. Run pc/apply
4. Plugin license now shows plain text key instead of env var

Expected behavior

Actual behavior

Craft CMS version

5.7.0

PHP version

8.2

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

[linear]

CMS-1733

[brandonkelly]

Save an env variable in a plugin license

Where are you saving that? In config/project.yaml or from Settings → Plugins?

[harry2909]

Save an env variable in a plugin license

Where are you saving that? In config/project.yaml or from Settings → Plugins?

We're saving it in settings -> plugins.

[brandonkelly]

Is the environment variable already defined when you enter it into the plugin’s license key input? If not, it’s expected that Craft will add it in .env.