Skip to content
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

Add encryption_settings to VMs and managed disks #16

Closed
wants to merge 2 commits into from

Conversation

StephenWeatherford
Copy link
Collaborator

@StephenWeatherford StephenWeatherford commented May 3, 2017

Add encryption_settings to virtual machines. Part 1 of fixing hashicorp#12259.

Working on tests.

@StephenWeatherford StephenWeatherford changed the title [WIP] Add encryption_settings to VMs Add encryption_settings to VMs (will add to managed disks afterwards) May 4, 2017
@StephenWeatherford StephenWeatherford changed the title Add encryption_settings to VMs (will add to managed disks afterwards) Add encryption_settings to VMs (will add to managed disks afterwards) - #12259 May 4, 2017
@StephenWeatherford StephenWeatherford changed the title Add encryption_settings to VMs (will add to managed disks afterwards) - #12259 Add encryption_settings to VMs (will add to managed disks afterwards) May 4, 2017

// Azure can change enabled from false to true, but not the other way around, so
// to keep idempotency, we'll conservatively set this to ForceNew=true
ForceNew: true,
Copy link
Collaborator

Choose a reason for hiding this comment

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

This means the existing disk will be deleted and a new one created. Data loss?

name = "standard"
}

tenant_id = "d6e396d0-5584-41dc-9fc0-268df99bc610"
Copy link
Collaborator

Choose a reason for hiding this comment

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

How is this going to work for others running the test?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Whoops, started but never finished.

version = "latest"
}

storage_os_disk {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Where is encryption_settings?

@StephenWeatherford
Copy link
Collaborator Author

StephenWeatherford commented May 4, 2017 via email

@StephenWeatherford StephenWeatherford changed the title Add encryption_settings to VMs (will add to managed disks afterwards) Add encryption_settings to VMs and managed disks May 6, 2017
@StephenWeatherford
Copy link
Collaborator Author

Creating new PR for hashicorp

@tomasquith
Copy link

@StephenWeatherford - Was this merged in as part of 0.10.0? I can't seem to see anything as part of the provider split

@StephenWeatherford
Copy link
Collaborator Author

I'm no longer working on terraform. @echuvyrov you took over this work, right? Is there a timeline?

@echuvyrov
Copy link
Collaborator

hey @tomasquith, the cadence for Terraform Core and providers is different now - AzureRM provider 0.1.5 was just released today while TF Core is at 0.10.0. I am going to finish up autoscale settings and then jump on this one, 2-3 weeks perhaps.

@tomasquith
Copy link

@StephenWeatherford @echuvyrov - Thanks for the updates.

We're about to start a major client deployment into Azure via Terraform, SSE for managed disks is a must - I really appreciate the work on this.

@StephenWeatherford's original PR has been moved to the provider repo -
hashicorp/terraform-provider-azurerm#157 - it looks like it just needs a few comments addressing before it can be merged. I'm happy to be a guinea pig and build off master when required?

@gudlyf
Copy link

gudlyf commented Aug 15, 2017

Saw the same pull request (hashicorp#157). Wondering where it's held up.

@tomasquith
Copy link

tomasquith commented Aug 16, 2017

@gudlyf - just a FYI, your linked PR is to an unrelated one, the correct PR is in the provider repo (since the split), with the same id. @echuvyrov stated a rough speculative timeline above :)

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