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

[Ubuntu] Allow image_sku to be passed in as variable #6756

Closed
wants to merge 1 commit into from

Conversation

ifutant
Copy link

@ifutant ifutant commented Dec 12, 2022

Description

This Pull Request seeks to modify the latest Ubuntu 22.04 Packer template to allow an override of the hard-coded image_sku. This change introduces a new variable, and contains the hard-coded value as its default.
The reason I desire to perform this override is to allow the deployment of a Generation 2 VM while consuming the packer template. I only targeted the images/linux/ubuntu2204.pkr.hcl file, because I didn't want to introduce a new variable dependency. I anticipate that this change will not impact current users of this packer template.

Additional Information:

Gen 2 VM Details

Check list

  • Related issue / work item is attached
  • Tests are written (if applicable)
  • Documentation is updated (if applicable)
  • Changes are tested and related VM images are successfully generated

@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 6756 in repo actions/runner-images

@ifutant
Copy link
Author

ifutant commented Dec 13, 2022

This is my first contribution to this repo. Is there anything else that I need to complete to obtain a review of this PR? @mikhailkoliada @maxim-lobanov @al-cheb @Alexey-Ayupov

@ifutant ifutant changed the title Allow image_sku to be passed in as variable [Ubuntu] Allow image_sku to be passed in as variable Dec 15, 2022
@mikhailkoliada
Copy link
Contributor

Hello! We do not plan using any alternative sku, so it makes little sense in general for us to use the variable here. So, we would not like to change it anyhow.

@ifutant
Copy link
Author

ifutant commented Dec 31, 2022

Why not introduce additional flexibility especially since Gen2 virtual machines are more modern? Just because your team doesn't plan to utilize an alternate SKU at the moment, that may not always be the case. What is the harm in making a small modification that facilities SKU parametrization while also maintaining existing functionality without impacting current users?

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.

2 participants