Skip to content

Conversation

@ranisha2
Copy link
Contributor

Update informationProtectionPolicies.json

  • Fix PUT: Missing parameter
  • Add missing parameters to the sensitivity label and information type

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

Update informationProtectionPolicies.json
- Fix PUT: Missing parameter
- Add missing parameters to the sensitivity label and information type
@weidongxu-microsoft weidongxu-microsoft added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Mar 11, 2020
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@bashahee bashahee self-assigned this Mar 11, 2020
@bashahee bashahee requested review from bashahee and removed request for bashahee March 11, 2020 11:55
@bashahee bashahee removed their assignment Mar 11, 2020
@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-go - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-js - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-java - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-net - Release

️✔️ succeeded [Logs] [Expand Details]

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 11, 2020

azure-sdk-for-python - Release

- Breaking Change detected in SDK

⚠️ warning [Logs] [Expand Details]
  • ⚠️ Generate from 040fb3a with merge commit fea3b43. SDK Automation 13.0.17.20200320.2
  • ⚠️azure-mgmt-security [Logs]  [Release SDK Changes] Breaking Change Detected
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'
    [build_package] /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
    [build_package]   warnings.warn(msg)
    [build_package] warning: no files found matching '*.py' under directory 'tests'
    [build_package] warning: no files found matching '*.yaml' under directory 'tests'
    [breaking_change_setup] Ignoring mock: markers 'python_version <= "2.7"' don't match your environment
    [breaking_change_setup] Cannot uninstall requirement azure-nspkg, not installed
    [breaking_change_setup] Command '['/usr/local/bin/python', '-m', 'pip', 'uninstall', '-y', 'azure-nspkg']' returned non-zero exit status 1.
    [ChangeLog] Size of delta 38.353% size of original (original: 116214 chars, delta: 44571 chars)
    [ChangeLog] **Features**
    [ChangeLog] 
    [ChangeLog]   - Model SensitivityLabel has a new parameter rank
    [ChangeLog]   - Model SensitivityLabel has a new parameter description
    [ChangeLog]   - Model IoTSecuritySolutionModel has a new parameter unmasked_ip_logging_status
    [ChangeLog]   - Model JitNetworkAccessRequest has a new parameter justification
    [ChangeLog]   - Model JitNetworkAccessPolicyInitiateRequest has a new parameter justification
    [ChangeLog]   - Model AppWhitelistingPutGroupData has a new parameter protection_mode
    [ChangeLog]   - Model VmRecommendation has a new parameter enforcement_support
    [ChangeLog]   - Model AppWhitelistingGroup has a new parameter protection_mode
    [ChangeLog]   - Model IoTSecurityAggregatedAlert has a new parameter top_devices_list
    [ChangeLog]   - Model InformationType has a new parameter description
    [ChangeLog]   - Added operation AlertsOperations.update_resource_group_level_alert_state_to_dismiss
    [ChangeLog]   - Added operation AlertsOperations.update_resource_group_level_alert_state_to_reactivate
    [ChangeLog]   - Added operation AlertsOperations.update_subscription_level_alert_state_to_dismiss
    [ChangeLog]   - Added operation AlertsOperations.update_subscription_level_alert_state_to_reactivate
    [ChangeLog]   - Added operation AdaptiveApplicationControlsOperations.delete
    [ChangeLog]   - Added operation IotSecuritySolutionOperations.create_or_update
    [ChangeLog]   - Added operation IotSecuritySolutionOperations.list_by_resource_group
    [ChangeLog]   - Added operation IotSecuritySolutionOperations.list_by_subscription
    [ChangeLog]   - Added operation group SubAssessmentsOperations
    [ChangeLog]   - Added operation group AssessmentsMetadataOperations
    [ChangeLog]   - Added operation group IotSecuritySolutionsAnalyticsAggregatedAlertOperations
    [ChangeLog]   - Added operation group AutomationsOperations
    [ChangeLog]   - Added operation group IotSecuritySolutionAnalyticsOperations
    [ChangeLog]   - Added operation group IotSecuritySolutionsAnalyticsRecommendationOperations
    [ChangeLog]   - Added operation group AdaptiveNetworkHardeningsOperations
    [ChangeLog]   - Added operation group AssessmentsOperations
    [ChangeLog]   - Added operation group DeviceSecurityGroupsOperations
    [ChangeLog] 
    [ChangeLog] **Breaking changes**
    [ChangeLog] 
    [ChangeLog]   - Operation JitNetworkAccessPoliciesOperations.initiate has a new signature
    [ChangeLog]   - Operation InformationProtectionPoliciesOperations.create_or_update has a new signature
    [ChangeLog]   - Removed operation AlertsOperations.update_subscription_level_alert_state
    [ChangeLog]   - Removed operation AlertsOperations.update_resource_group_level_alert_state
    [ChangeLog]   - Removed operation IotSecuritySolutionOperations.create
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsAnalyticsAggregatedAlertOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsAnalyticsRecommendationOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsResourceGroupOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsAnalyticsAggregatedAlertsOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsAnalyticsOperations
    [ChangeLog]   - Removed operation group IoTSecuritySolutionsAnalyticsRecommendationsOperations

@bashahee
Copy link
Contributor

@weidongxu-microsoft can this PR be merged?

The existing swagger is invalid, hence the failures in this PR's tests. Moreover, existing SDK clients are not usable now, so we need this swagger merged in order to update SDK clients package with working clients.

@weidongxu-microsoft
Copy link
Member

@bashahee

I will email arm review on this, with your reason here (this is still a needed step). Then I will ask PM to force merge.

@bashahee
Copy link
Contributor

Thanks @weidongxu-microsoft for the help!

@pilor pilor added ARMReviewInProgress ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMReviewInProgress WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Mar 24, 2020
@weidongxu-microsoft
Copy link
Member

@akning-ms Can you help merge this?

BreakingChange is due to existing swagger is invalid (hence this PR).

@weidongxu-microsoft weidongxu-microsoft added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Mar 25, 2020
@weidongxu-microsoft weidongxu-microsoft removed their assignment Mar 26, 2020
@akning-ms akning-ms merged commit fea3b43 into Azure:master Mar 26, 2020
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Mar 26, 2020

azure-cli-extensions - Release

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

00Kai0 pushed a commit to 00Kai0/azure-rest-api-specs that referenced this pull request Oct 12, 2020
* Update informationProtectionPolicies.json

Update informationProtectionPolicies.json
- Fix PUT: Missing parameter
- Add missing parameters to the sensitivity label and information type

* Update CreateOrUpdateInformationProtectionPolicy_example.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants