Skip to content

ADL Preview Release Update#2803

Merged
cormacpayne merged 7 commits intoAzure:AutoRestfrom
begoldsm:AutoRest
Feb 13, 2017
Merged

ADL Preview Release Update#2803
cormacpayne merged 7 commits intoAzure:AutoRestfrom
begoldsm:AutoRest

Conversation

@begoldsm
Copy link
Copy Markdown
Contributor

@begoldsm begoldsm commented Feb 9, 2017

Description

This update includes the following:

  • Firewall support for ADLA
  • Enable Azure IPs through firewall in both ADLA and ADLS
  • Add Patch support for Firewall and Trusted Identity Provider
  • Fix bug in GetContentSummary in ADLS

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
  • The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@begoldsm
Copy link
Copy Markdown
Contributor Author

begoldsm commented Feb 9, 2017

Here is the Swagger PR: Azure/azure-rest-api-specs#897

Copy link
Copy Markdown
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@begoldsm couple of comments for clarification

"Microsoft.Azure.Management.DataLake.Analytics": "[1.0.1-preview,2.0.0)",
"Microsoft.Azure.Management.DataLake.Store": "[1.0.1-preview,2.0.0)",
"Microsoft.Azure.Management.DataLake.Analytics": "[2.0.0-preview, 3.0.0-preview)",
"Microsoft.Azure.Management.DataLake.Store": "[2.0.0-preview, 3.0.0-preview)",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@begoldsm should these both be 2.0.1-preview?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good call, explicitly updated.

"Microsoft.Rest.ClientRuntime": "[2.3.2,3.0)" ,
"Microsoft.Azure.ResourceManager": "1.0.0-preview",
"Microsoft.Azure.Management.DataLake.Store": "2.0.0-preview",
"Microsoft.Azure.Management.DataLake.Store": "[2.0.0-preview, 3.0.0-preview)",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@begoldsm same comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

same answer :)

/// 'Commitment_10TB', 'Commitment_100TB', 'Commitment_500TB',
/// 'Commitment_1PB', 'Commitment_5PB'</param>
public DataLakeStoreAccountUpdateParameters(IDictionary<string, string> tags = default(IDictionary<string, string>), FirewallState? firewallState = default(FirewallState?), TrustedIdProviderState? trustedIdProviderState = default(TrustedIdProviderState?), string defaultGroup = default(string), TierType? newTier = default(TierType?))
public DataLakeStoreAccountUpdateParameters(IDictionary<string, string> tags = default(IDictionary<string, string>), FirewallState? firewallState = default(FirewallState?), FirewallAllowAzureIpsState? firewallAllowAzureIps = default(FirewallAllowAzureIpsState?), TrustedIdProviderState? trustedIdProviderState = default(TrustedIdProviderState?), string defaultGroup = default(string), TierType? newTier = default(TierType?))
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@begoldsm changing parameter order is a breaking change - should be fine since you are preview

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Oh good catch, and this is interesting. I wanted to keep all firewall related stuff together, but I am open to suggestions here. Do you think we should always just append parameters to the back, even when we are going to preview? This breaking change won't come in to stable for some time, and it will result in a major version bump (from 1.* to 2.*). Thoughts?

@cormacpayne
Copy link
Copy Markdown
Member

LGTM

@cormacpayne cormacpayne merged commit 1fd56fe into Azure:AutoRest Feb 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants