providers.Interface: rename ValidateDataSourceConfig to ValidateDataResourceConfig (#27874)

* providers.Interface: rename ValidateDataSourceConfig to
ValidateDataResourceConfig

This PR came about after renaming ValidateResourceTypeConfig to
ValidateResourceConfig: I now understand that we'd called it the former
instead of the latter to indicate that the function wasn't necessarily
operating on a resource that actually exists. A possibly-more-accurate
renaming of both functions might then be ValidateManagedResourceConfig
and ValidateDataResourceConfig.

The next commit will update the protocol (v6 only) as well; these are in
separate commits for reviewers and will get squashed together before
merging.

* extend renaming to protov6
This commit is contained in:
Kristin Laemmert
2021-02-24 12:04:28 -05:00
committed by GitHub
parent 21d881d4d1
commit ff05362d51
20 changed files with 339 additions and 338 deletions

View File

@@ -146,7 +146,7 @@ service Provider {
rpc GetProviderSchema(GetProviderSchema.Request) returns (GetProviderSchema.Response);
rpc ValidateProviderConfig(ValidateProviderConfig.Request) returns (ValidateProviderConfig.Response);
rpc ValidateResourceConfig(ValidateResourceConfig.Request) returns (ValidateResourceConfig.Response);
rpc ValidateDataSourceConfig(ValidateDataSourceConfig.Request) returns (ValidateDataSourceConfig.Response);
rpc ValidateDataResourceConfig(ValidateDataResourceConfig.Request) returns (ValidateDataResourceConfig.Response);
rpc UpgradeResourceState(UpgradeResourceState.Request) returns (UpgradeResourceState.Response);
//////// One-time initialization, called before other functions below
@@ -222,7 +222,7 @@ message ValidateResourceConfig {
}
}
message ValidateDataSourceConfig {
message ValidateDataResourceConfig {
message Request {
string type_name = 1;
DynamicValue config = 2;