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

provider/azurerm: Add azurerm_virtual_machine_scale_set resource #6711

Merged
merged 1 commit into from
Jun 10, 2016

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented May 17, 2016

  • Schema
  • CRUD
  • Acceptance Tests
  • Documentation
make testacc TEST=./builtin/providers/azurerm TESTARGS='-run=TestAccAzureRMVirtualMachineScaleSet'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /vendor/)
TF_ACC=1 go test ./builtin/providers/azurerm -v -run=TestAccAzureRMVirtualMachineScaleSet -timeout 120m
=== RUN   TestAccAzureRMVirtualMachineScaleSet_basicLinux
--- PASS: TestAccAzureRMVirtualMachineScaleSet_basicLinux (706.89s)

@stack72 stack72 force-pushed the arm-vm-scalesets branch 2 times, most recently from b160379 to 2d9e677 Compare May 17, 2016 17:24
@stack72 stack72 force-pushed the arm-vm-scalesets branch 3 times, most recently from 90ad0ba to 38d3c83 Compare May 27, 2016 18:25
@stack72 stack72 force-pushed the arm-vm-scalesets branch 2 times, most recently from e0cb175 to 9c91ff6 Compare June 10, 2016 21:59
@stack72 stack72 changed the title [WIP] provider/azurerm: Add azurerm_virtual_machine_scale_set resource provider/azurerm: Add azurerm_virtual_machine_scale_set resource Jun 10, 2016
m := v.(map[string]interface{})
buf.WriteString(fmt.Sprintf("%s-", m["name"].(string)))
//buf.WriteString(fmt.Sprintf("%v-", m["caching"].(string)))
//buf.WriteString(fmt.Sprintf("%v-", m["create_option"].(string)))
Copy link
Contributor

Choose a reason for hiding this comment

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

Commented bits here. Not sure if they need to be in or are a TODO?

@stack72 stack72 force-pushed the arm-vm-scalesets branch 2 times, most recently from efb172e to 4b1f9f8 Compare June 10, 2016 22:19
@phinze
Copy link
Contributor

phinze commented Jun 10, 2016

Looking great overall! Some in line Qs for you above, and one overall question on attr naming ->

I see that a lot of the blocks are virtual_machine_{thing} - I understand this is flattening to work around helper/schema's problems dealing with deeply nested structs. I wonder if so much of the config is virtual_machine_ prefixed that it might make sense to drop that?

I think once we get the deep-nested attributes bugs sorted we'll move everything over to that, but in the meantime just a thought that might make the "flattened workaround" style config a big cleaner.

@phinze
Copy link
Contributor

phinze commented Jun 10, 2016

LGTM with edits!

@stack72 stack72 merged commit 514d842 into master Jun 10, 2016
@stack72 stack72 deleted the arm-vm-scalesets branch June 10, 2016 22:37
@ghost
Copy link

ghost commented Apr 25, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants