Skip to content

Conversation

@yaborens
Copy link
Contributor

@yaborens yaborens commented Dec 6, 2018

…anagement/preview/2018-08-01-preview/costmanagement.json

Add more Scopes to Alerts.
Also, add /updateStatus to Alerts

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.

…anagement/preview/2018-08-01-preview/costmanagement.json

Add more Scopes to Alerts.
Also add /updateStatus to Alerts
@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-ruby

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-ruby#1970

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Dec 6, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#3749

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@praries880 praries880 added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Dec 6, 2018
Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes seem fine. one question in comments

@KrisBash KrisBash added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Dec 7, 2018
@yaborens
Copy link
Contributor Author

yaborens commented Dec 9, 2018

@KrisBash , @praries880 Who can merge the code? as I'm not authorized to merge this pull request

},
{
"name": "$filter",
"description": "May be used to filter alerts by properties/definition/type, properties/definition/category, properties/definition/criteria, properties/costEntityId, properties/creationTime, properties/closeTime, properties/status, properties/source. Supported operators are 'eq','lt', 'gt', 'le', 'ge'.",
Copy link

@praries880 praries880 Dec 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborens
Examples corresponding to this change?

Also, is the list of filters a closed list? If so... why not use an enum?

Copy link
Contributor Author

@yaborens yaborens Dec 12, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Examples corresponding to this change? sorry but I don't understand the question

is the list of filters a closed list? If so... why not use an enum? this is how all other groups implemented a filter.

Copy link

@praries880 praries880 Dec 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborens
Here are the changes to the example linked here : https://github.com/Azure/azure-rest-api-specs/pull/4818/files/1d5c0565121e5fef4897b32e78318df919406717#diff-cd2cdd86afbc1836331eaef83f213b9cR30

Is that all that changes there for the new API added here?

As for the supported values for the "filter" parameter from the description above : "properties/definition/type, properties/definition/category, properties/definition/criteria, properties/costEntityId, properties/creationTime, properties/closeTime, properties/status, properties/source", is this a list that changes dynamically? If not, then why not model it as an enum?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,
Is that all that changes there for the new API added here? yes

  • Filter is not a close group, thus it cannot be enum.
  • properties/definition/type - not a close group, thus it cannot be enum.
  • properties/definition/category - Already an Enum
  • properties/definition/criteria - Already an Enum
  • properties/costEntityId - not a close group, thus it cannot be enum.
  • properties/creationTime- Not an Enum field
  • properties/closeTime - Not an Enum field
  • properties/status - Already an Enum
  • properties/source - Already an Enum

Copy link

@praries880 praries880 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborensth Some comments

},
{
"name": "$filter",
"description": "May be used to filter alerts by properties/definition/type, properties/definition/category, properties/definition/criteria, properties/costEntityId, properties/creationTime, properties/closeTime, properties/status, properties/source. Supported operators are 'eq','lt', 'gt', 'le', 'ge'.",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborens
Examples corresponding to this change?

Also, is the list of filters a closed list? If so... why not use an enum?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comments as above

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see only this change in the example linked here : https://github.com/Azure/azure-rest-api-specs/pull/4818/files/1d5c0565121e5fef4897b32e78318df919406717#diff-cd2cdd86afbc1836331eaef83f213b9cR30

Is that all changes in the example for this new API?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

},
{
"name": "$filter",
"description": "May be used to filter alerts by properties/definition/type, properties/definition/category, properties/definition/criteria, properties/costEntityId, properties/creationTime, properties/closeTime, properties/status, properties/source. Supported operators are 'eq','lt', 'gt', 'le', 'ge'.",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborens
Examples corresponding to this change?

Also, is the list of filters a closed list? If so... why not use an enum?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comments as above

},
{
"name": "$filter",
"description": "May be used to filter alerts by properties/definition/type, properties/definition/category, properties/definition/criteria, properties/costEntityId, properties/creationTime, properties/closeTime, properties/status, properties/source. Supported operators are 'eq','lt', 'gt', 'le', 'ge'.",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaborens
Examples corresponding to this change?

Also, is the list of filters a closed list? If so... why not use an enum?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comments as above

@praries880 praries880 merged commit e74dde5 into Azure:master Dec 17, 2018
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
* Update specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2018-08-01-preview/costmanagement.json

Add more Scopes to Alerts.
Also add /updateStatus to Alerts

* Add billing parameter to departments

* Add alert parameters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

5 participants