Skip to content

[storage] Support enable large file shares #10276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 15, 2019

Conversation

blueww
Copy link
Member

@blueww blueww commented Oct 14, 2019

Description

The design pass review in: Azure/azure-powershell-cmdlet-review-pr#386

The PR has already been merged to storage preview branch before : #10234

This workitem is tracking it.: #10263

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • the markdown help files have been regenerated using the commands listed here

Copy link
Contributor

@wyunchi-ms wyunchi-ms left a comment

Choose a reason for hiding this comment

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

Why using _ here instead of using CamelCase?

Comment on lines +161 to +163
public void TestNewSetAzureStorageAccount_LargeFileShare()
{
TestRunner.RunTestScript("Test-NewSetAzureStorageAccount_LargeFileShare");
Copy link
Contributor

Choose a reason for hiding this comment

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

Why using _ here instead of using CamelCase?

Copy link
Member Author

@blueww blueww Oct 15, 2019

Choose a reason for hiding this comment

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

@wyunchi-ms
Does it break any rule?
I use _ since the NewSetStorageAccount is long and want to show what's the case really test more obviously
I don't prefer to change it, since it will take difficulty to merge changes back to storage branch.
Anyway, if it do break some name rules, I can change it.

.DESCRIPTION
SmokeTest
#>
function Test-NewSetAzureStorageAccount_LargeFileShare
Copy link
Contributor

Choose a reason for hiding this comment

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

Why using _ here instead of using CamelCase?

Copy link
Member Author

Choose a reason for hiding this comment

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

same as above.

@wyunchi-ms wyunchi-ms merged commit a590205 into Azure:master Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants