Remove CostTags from Consumption Specs

[asarkar84]

Remove CostTags from Consumption Specs

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-python

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-python#2158

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[AutorestCI]

Automation for azure-sdk-for-node

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-node#3319

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

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-go#2455

[asarkar84]

@marstr Please take a look at this PR.

[marstr]

Howdy @asarkar84, this is a pretty real breaking change. Can you explain the context as to why the CostTag stuff was added in the first place?

edit: grammar

[asarkar84]

Hello @marstr , The consumption cost tags and the cost tags by Cloudyn are similar and conflicting features. We have got instructions to hide this functionality until we decide which one lives. There is no CostTags created until now so it is still safe to hide it.

[marstr]

Given that this a non-preview API Version, and the swagger has been marked as stable, these sorts of changes should really, really be in a new API Version. They represent fundamental changes to what customers are able to do with your service, and as such is a huge breaking change to anybody trying to use your product regardless of whether or not they're using AutoRest generated clients or curl.

[asarkar84]

As per the discussion over the email, closing the PR.