* first pass at pulling in VMSS data
* infer vmss set id and external name from vmss data as none of these items are present by default
* updated scale set name formatting to align with azure portal and json outputs
* Update plugin/plugin.go
Updated following code review
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* Update plugin/plugin.go
Updated following code review
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* complete refactoring of initial implementation following code review, taking into accounts comments and common sense updates
* updated README.md to reflect changes to support VMSS
* fixed typo in README.md
* WIP: initial updates following code review
* refactored resource functions
* removed instrumentation statements
* resolve ifname comments
* address formatting issues in accordance with style recommendations
---------
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
It turns out you can't filter on both resource type and tags at the same
time, which means checking type needs to happen in code. Additionally,
you can't request provisioning state because populating $expand also
does bad things when using tags in filters.
Benjamin HolmesandJohan Brandhorst-Satzkorn
hashicorp-copywrite[bot]
Jeff Mitchell