-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
We have an init container that creates a PrivateLink connection on start. So we have an acceptance test that tests the data source using that PrivateLink connection ID:
terraform-provider-materialize/pkg/provider/acceptance_datasource_connection_test.go
Lines 34 to 39 in 73bd471
| // TODO: Test intermittently fails | |
| // resource.TestCheckResourceAttr("data.materialize_connection.specific", "connection_id", "u1"), | |
| // resource.TestCheckResourceAttr("data.materialize_connection.specific", "connections.#", "1"), | |
| // resource.TestCheckResourceAttr("data.materialize_connection.specific", "connections.0.id", "u1"), | |
| // resource.TestCheckResourceAttr("data.materialize_connection.specific", "connections.0.name", "privatelink_conn"), | |
| // Cannot ensure the exact number of objects with parallel tests |
terraform-provider-materialize/pkg/provider/acceptance_datasource_connection_test.go
Lines 73 to 75 in 73bd471
| # data "materialize_connection" "specific" { | |
| # connection_id = "u1" | |
| # } |
However, in CI this test would fail intermittently with a no results found error. Locally this works as expected each time.
The test is disabled for the moment to prevent the intermittent failing, but will be nice to have it re-enabled once we know why it fails intermittently in CI.
Metadata
Metadata
Assignees
Labels
No labels