You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the work on #53 we noticed that the code for connecting a tf resource to a ProviderConfig isn't being tested right now.
This refers to the two methods called TerraformSetupBuilder and TerraformSetupBuilderNoTracking (see here). While the first one is being used for any upjetted resource type the second one is being used specifically within ServiceManager and CloudManagement, where we have a native controller then internally delegates to a tf resource.
It probably makes sense to also combine those methods while we are at it. You can refer to similar tests like the ones for the rolecollection resource here.
Expected Outcome
TerraformSetupBuilder and TerraformSetupBuilderNoTracking are covered by unittests
The text was updated successfully, but these errors were encountered:
Context
During the work on #53 we noticed that the code for connecting a tf resource to a
ProviderConfig
isn't being tested right now.This refers to the two methods called
TerraformSetupBuilder
andTerraformSetupBuilderNoTracking
(see here). While the first one is being used for any upjetted resource type the second one is being used specifically within ServiceManager and CloudManagement, where we have a native controller then internally delegates to a tf resource.It probably makes sense to also combine those methods while we are at it. You can refer to similar tests like the ones for the rolecollection resource here.
Expected Outcome
TerraformSetupBuilder
andTerraformSetupBuilderNoTracking
are covered by unittestsThe text was updated successfully, but these errors were encountered: