Skip to content

Add support for querying encryption status from the AzureDiskEncryptionForLinux extension #2849

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 28 commits into from
Sep 1, 2016

Conversation

krkhan
Copy link

@krkhan krkhan commented Aug 28, 2016

Mandatory = false,
Position = 2,
ValueFromPipelineByPropertyName = true,
HelpMessage = "The extension name. If this parameter is not specified, default values used are AzureDiskEncryption for windows VMs and AzureDiskEncryptionForLinux for Linux VMs")]
Copy link
Contributor

Choose a reason for hiding this comment

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

capitalize "windows" -> "Windows"

Copy link
Author

Choose a reason for hiding this comment

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

Fixed with d4d5774

@markcowl
Copy link
Member

markcowl commented Aug 30, 2016

@krkhan please respond to review comments. ALso, please clean up the number of commits and commit comments, by cherry-picking or rebasing the commits.

@krkhan
Copy link
Author

krkhan commented Aug 30, 2016

@markcowl Addressed comments on both GH and CF. Added you to the CF review as well.

@markcowl
Copy link
Member

on demand run here:http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1125/

LGTM once this passes

@krkhan
Copy link
Author

krkhan commented Aug 30, 2016

@markcowl That error doesn't look related to disk encryption.

d:\workspace\powershell-demand\src\ResourceManager\Sql\Commands.Sql.Test\ScenarioTests\SqlTestsBase.cs(76): error : Microsoft.Azure.Commands.Sql.Test.ScenarioTests.ThreatDetectionTests.ThreatDetectionGetDefualtPolicy [FAIL] [D:\workspace\powershell-demand\build.proj]

@markcowl
Copy link
Member

@krkhan It isn't, you need to rebase this change on the latest in the dev branch, as there is a fix for this issue there.on the

@cormacpayne
Copy link
Member

@krkhan Hey Kamran, the test that is failing in your on-demand build has been fixed and merged into dev, so if you pull and rebase with dev, you should be fine.

You can check out how to rebase in our cleaning up commits guide

@markcowl
Copy link
Member

@krkhan, we can't merge until you do this

@krkhan
Copy link
Author

krkhan commented Aug 31, 2016

There's a minor CR change that's needed. I'll do that today as well as merge upstream dev so that the fix is pulled in.

@ejarvi
Copy link
Contributor

ejarvi commented Aug 31, 2016

@markcowl finished reviewing, looks good

@krkhan
Copy link
Author

krkhan commented Aug 31, 2016

@markcowl markcowl merged commit 68a90d2 into Azure:dev Sep 1, 2016
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.

5 participants