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

Fix merge error #28423

Merge branch 'curiekim0-databricks-Microsoft.Databricks-2024-05-01' i…

3378765
Select commit
Loading
Failed to load commit list.
Merged

Fix merge error #28423

Merge branch 'curiekim0-databricks-Microsoft.Databricks-2024-05-01' i…
3378765
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / ~[NotRequired_Staging] Swagger LintDiff succeeded Mar 24, 2024 in 5m 5s

~[NotRequired_Staging] Swagger LintDiff succeeded

Details

compared tags (via openapi-validator vbeta) new version base version
package-2024-05-01 package-2024-05-01(3378765) package-2024-05-01(curiekim0-databricks-Microsoft.Databricks-2024-05-01)

[must fix]The following errors/warnings are introduced by current PR:

Rule Message Related RPC [For API reviewers]
⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1183
⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1177


The following errors/warnings exist before current PR submission:
Only 50 items are listed, please refer to log for more details.

Rule Message
XmsParameterLocation The parameter 'ApiVersionParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1963
XmsParameterLocation The parameter 'SubscriptionIdParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1956
MissingTypeObject The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1657
MissingTypeObject The schema 'display' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1634
PropertiesTypeObjectNoDefinition Properties with type:object that don't reference a model definition are not allowed. ARM doesn't allow generic type definitions as this leads to bad customer experience.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1614
MissingTypeObject The schema 'WorkspaceListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1610
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1522
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1517
MissingTypeObject The schema 'WorkspaceProviderAuthorization' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1513
MissingTypeObject The schema 'keyVaultProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1437
MissingTypeObject The schema 'EncryptionV2' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1424
MissingTypeObject The schema 'EncryptionEntitiesDefinition' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1409
MissingTypeObject The schema 'Encryption' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1354
MissingTypeObject The schema 'WorkspaceEncryptionParameter' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1341
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1334
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1323
MissingTypeObject The schema 'CreatedBy' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1319
PropertiesTypeObjectNoDefinition Properties with type:object that don't reference a model definition are not allowed. ARM doesn't allow generic type definitions as this leads to bad customer experience.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1305
MissingTypeObject The schema 'WorkspaceCustomParameters' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1243
MissingTypeObject The schema 'WorkspaceCustomStringParameter' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1227
PropertiesTypeObjectNoDefinition Properties with type:object that don't reference a model definition are not allowed. ARM doesn't allow generic type definitions as this leads to bad customer experience.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1217
MissingTypeObject The schema 'WorkspaceCustomObjectParameter' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1211
MissingTypeObject The schema 'WorkspaceCustomBooleanParameter' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1195
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1060
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1054
MissingTypeObject The schema 'ManagedIdentityConfiguration' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L1049
MissingTypeObject The schema 'Sku' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L996
MissingTypeObject The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L975
MissingTypeObject The schema 'TrackedResource' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L942
PropertiesTypeObjectNoDefinition Properties with type:object that don't reference a model definition are not allowed. ARM doesn't allow generic type definitions as this leads to bad customer experience.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L763
MissingTypeObject The schema 'WorkspaceProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L757
PropertiesTypeObjectNoDefinition Properties with type:object that don't reference a model definition are not allowed. ARM doesn't allow generic type definitions as this leads to bad customer experience.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L731
MissingTypeObject The schema 'Workspace' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L729
XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L685
ResourceNameRestriction The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L684
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L678
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L666
DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L634
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L629
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L620
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L573
ProvisioningStateSpecifiedForLROPut 201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L573
ResourceNameRestriction The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L528
ResourceNameRestriction The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L482
ResourceNameRestriction The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L436
ResourceNameRestriction The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L390
OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L375
OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.Databricks/operations' does not match the ARM specification. Please standardize the schema.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L374
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L261
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Databricks/stable/2024-05-01/databricks.json#L258