[BUG] Consider scaffold/apply scenarios where the connection name is defined as a CONFIG_VARIABLE

[carlosmscabral]

Describe the bug
If in my Integration, in the connnection tasks, I set the connection name as as CONFIG_VARIABLE, the scaffold command creates an overrides item like so:

{
	"connection_overrides": [
		{
			"taskId": "1",
			"task": "GenericConnectorTask",
			"parameters": {
				"connectionName": "vertex-connection"
			}
		}
	],

The CONFIG_VARIABLE is correctly exported under the config-variables folder. But it gets... inconsistent.

When I apply the integration, it seems somehow to "render" / ignore the CONFIG_VARIABLE configuration from scaffold instead of CONFIG_VAR.

Version
Version of the cli being used (run integrationcli --version)
integrationcli version 0.78.0 date: 2024-12-10T17:57:38Z [commit: 9371c4e]

To Reproduce
See details above.

Additional context
Add any other context about the problem here.

[ssvaidyanathan]

@srinandan - is this still the case?