Skip to content

[HDInsight] Fix Error Operation returned an invalid status code 'NotFound' when using New-AzHDInsightCluster with ADLS #10306

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 17, 2019
Merged

[HDInsight] Fix Error Operation returned an invalid status code 'NotFound' when using New-AzHDInsightCluster with ADLS #10306

merged 1 commit into from
Oct 17, 2019

Conversation

aim-for-better
Copy link
Member

@aim-for-better aim-for-better commented Oct 16, 2019 •
edited
Loading

Description

  1. Add ApplicationId to AddAzureHDInsightClusterIdentity,NewAzureHDInsightClusterCommand,
    NewAzureHDInsightClusterConfigCommand.
  2. Update related help doc and related unit test
  3. update change log

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

1. Add ApplicationId to AddAzureHDInsightClusterIdentity,NewAzureHDIn…
74b084a 
…sightClusterCommand,

NewAzureHDInsightClusterConfigCommand.
2. Update related help doc and related unit test
3. update change log
@aim-for-better aim-for-better force-pushed the FixResource404WhenCreateCluster branch from c98e7c3 to 74b084a Compare October 16, 2019 10:28
@wyunchi-ms wyunchi-ms self-assigned this Oct 17, 2019
@wyunchi-ms
Copy link
Contributor

wyunchi-ms commented Oct 17, 2019 •
edited
Loading

PS. Adding ApplicationId will fix the error, right? @aim-for-better

@aim-for-better
Copy link
Member Author

PS. Adding ApplicationId will fix the error, right? @aim-for-better

Yes. In fact, there is no bug. But we can provide a better service by adding ApplicationId parameter.

@wyunchi-ms wyunchi-ms merged commit 23b4589 into Azure:master Oct 17, 2019
@wyunchi-ms
Copy link
Contributor

got it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@wyunchi-ms wyunchi-ms wyunchi-ms approved these changes

Assignees

@wyunchi-ms wyunchi-ms

Labels
needs-review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@aim-for-better @wyunchi-ms @azuresdkci