feat(azure): baking from another existing image

[nemesisOsorio]

• Fixing azure baking for windows images
  • Producing a managed image instead a VHD(VHD will be deprecated, baking Linux images is already producing a managed image)
• Migrating JSON templates to HCL (JSON templates will be deprecated)
• Adding the option to bake from another existing image using:
  • publisher, offer and sku
  • another managed image

Related PRs

• feat(Azure): Listing managed images from Azure account in BaseOs drop. deck#9896
• feat(azure): Fetch Azure managed images from the managed images namespace cache clouddriver#5795

[spinnakerbot]

We prefer that non-test backend code be written in Java or Kotlin, rather than Groovy. The following files have been added and written in Groovy:

• rosco-core/src/main/groovy/com/netflix/spinnaker/rosco/providers/azure/util/AzureImageNameFactory.groovy

See our server-side commit conventions here.

[sergio-quintero]

I'm just curious: Is there a reason to set this to 20s instead of the old value 30s? I noticed it in the azure-linux.pkr.hcl as well.

[nemesisOsorio]

no specific reason, I believe it is to give the VM the chance to be ready, 20s worked well, and I considered removing them even