SAUCE_TUNNEL_IDENTIFIER environment variable is ignored

[Shplorf]

Ideally if this variable is present, that tunnel identifier would be used and a new tunnel would not be created. Currently this variable is ignored.

My use case is running tests against a QA environment inside a VPC, so I use a Sauce Connect Proxy which has its own tunnel identifier that I want my tests to use. Currently there is no way to configure this.

[AndreyBelym]

Hello @Shplorf! Looks like you mixed 2 cases in your proposal:

1. You want to create a new tunnel with a predefined identifier. We can introduce SAUCE_TUNNEL_IDENTIFIER variable for that case.

2. You want to reuse an already established tunnel with the given identifier. In this case we introduce TESTCAFE_REUSE_SAUCE_TUNNEL variable.

We will implement it in a couple of weeks, stay tuned!

[adback03]

Any updates on this?

[bryant-sfdo]

Has any work been done on this @AndreyBelym? I'm running into a scenario where I need this supported as well.

[chauncey-garrett]

@AndreyBelym This is something we need as well since we have a Sauce Connect Pool as described below already in place.

https://wiki.saucelabs.com/display/DOCS/High+Availability+Sauce+Connect+Proxy+Setup

[Farfurix]

@adback03, @bryant-sfdo, @chauncey-garrett

Hello,

At present, we don't work on this functionality and I can't give you any time estimates when we can implement it.

In the meantime, you are welcome to submit your PR.

[alexgriffen]

This seems to work for me with a config.json file:

{
  "tunnelIdentifier":"TUNNEL_ID",
  "username":"USERIDHERE",
  "accessKey":"ACCESSKEYHERE",
  "build": "testcafe"
}

The plugin still creates a tunnel, but Sauce uses the tunnel I pass for tunnelIdentifier for the tests. It's not perfect, but if you don't mind the plugin creating an unused/unnamed tunnel, this works.