Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
carlosmscabral opened this issue Dec 11, 2024 · 0 comments

Comments

@carlosmscabral
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant