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

azurerm_orchestrated_virtual_machine_scale_set - fix source_image_id processing #17786

Closed
wants to merge 1 commit into from

Conversation

thefisk
Copy link

@thefisk thefisk commented Jul 28, 2022

This is a proposed fix for issue #14820

As discussed in the issue, there is an issue with the azurerm_orchestrated_virtual_machine_scale_set resource, whereby the source_image_id attribute is not sent through to the Azure API. This is a result of an error in the expandOrchestratedSourceImageReference function. We can see on lines 1339-1341 that the function will exit before checking the source_image_id value if the source_image_reference block is empty, which it should be if a source_image_id is provided.

As mentioned, I'm not sure if the prefered fix would be to fix the new function, or simply to make a call to the pre-existing expandSourceImageReference like I have done in this PR. Either way, I figured opening this PR would be a good start to getting this issue resolved as it's been outstanding for 7 months.

@WodansSon
Copy link
Collaborator

@thefisk, thank you so much for opening this PR. I am currently working on adding fields to VMSS in PR #17571 and I will pull the fix into that PR to keep everything a bit cleaner. We like to keep the expand and flatten functions separate for Uniform and Orchestrated versions of the VMSS because of the way the service team implements new features into the API. For that reason I will be closing this PR and adding the fix to the existing #17571. Thanks again! 🚀

@WodansSon WodansSon closed this Jul 29, 2022
@thefisk
Copy link
Author

thefisk commented Jul 30, 2022

Thanks again for confirming, @WodansSon

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants