Renamed BuildTask to FileTask and RunTask to EncodedTask in Azure Container registry Build GA swagger

[mnltejaswini]

We have renamed some of the data models to reflect the data they represent. The example files are updated to reflect the new data models. There is no other change in the API.

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-ruby

Nothing to generate for azure-sdk-for-ruby

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-python

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

[AutorestCI]

Automation for azure-sdk-for-node

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

[AutorestCI]

Automation for azure-sdk-for-go

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

[AutorestCI]

Automation for azure-sdk-for-java

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

[mnltejaswini]

@jhendrixMSFT The SDKs for this swagger haven't yet merged in, It is still in development phase. So is it still a breaking change?

[jhendrixMSFT]

@mnltejaswini Merging a swagger into this repo is considered a release event (we have already released an SDK for this swagger in the Go programming language). In addition, this swagger is in a stable directory.

[mnltejaswini]

@jhendrixMSFT I see, thank you. Although the SDKs are available, the API is not yet available and exposed in ARM. so there aren't any potential customers

[jhendrixMSFT]

@mnltejaswini When will the API be available? We should never merge a swagger into the public repo if the backing APIs aren't available.

[mnltejaswini]

@jhendrixMSFT They will be available by 9/4

[jhendrixMSFT]

@johanste @ravbhatnagar do we leave this swagger until the release date?

[johanste]

@jhendrixMSFT - yes. We should update the title to include a [DO NOT MERGE] with this information included.