Skip to content

added supported TrafficAnalyticsInterval values in documentation for Set-AzNetworkWatcherConfigFlowLog #13304

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 26, 2020
Merged

Conversation

MariachiForHire
Copy link
Contributor

@MariachiForHire MariachiForHire commented Oct 22, 2020

Description

I added the supported values in the documentation for the TrafficAnalyticsInterval parameter in the Set-AzNetworkWatcherConfigFlowLog module.

ErrorCode: InvalidFlowLogTrafficAnalyticsInterval
ErrorMessage: Invalid traffic analytics interval 5. Supported values are 10 and 60 minutes.

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

@ghost
Copy link

ghost commented Oct 22, 2020

Thank you for your contribution MariachiForHire! We will review the pull request and get back to you soon.

@isra-fel
Copy link
Member

Thanks for the contribution : )
@sayghosh could you help review the change or suggest someone else? Thank you!

@sayghosh
Copy link
Contributor

The change looks good to me.

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run azure-powershell - windows-powershell

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@isra-fel
Copy link
Member

/azp run azure-powershell - windows-powershell

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@isra-fel
Copy link
Member

/azp run azure-powershell - windows-powershell

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@isra-fel isra-fel merged commit 373a640 into Azure:master Oct 26, 2020
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.

4 participants