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

Feature Request - Azure (ARM) Postprocessor #6281

Closed
flamarion opened this issue May 17, 2018 · 6 comments
Closed

Feature Request - Azure (ARM) Postprocessor #6281

flamarion opened this issue May 17, 2018 · 6 comments

Comments

@flamarion
Copy link

Hi,

I am a daily user of Packer and I'd like to ask you guys to try implement some post-processors for Azure like we have for AWS.

Currently, after all my builds (virtualbox-iso, for example) which I need to push the result to Azure, I need to do it using a post-processor shell and wrap Python + Virtualenv + AzureCLI.

To use these tools is not a problem at all, but the post-processor is being really big and complex due the nature of build (We need to do some conversions and resizes to be accepted by Azure) so the part to push the result of all those complexity could be facilitated with a post-processor able to create a managed image and VHD.

Thank you,

Flamarion Jorge

@flamarion flamarion changed the title Azure (ARM) Postprocessor Feature Request - Azure (ARM) Postprocessor May 17, 2018
@boumenot
Copy link
Collaborator

boumenot commented May 17, 2018

Is this similar to #6101? It sounds like there is some overlap (size alignment?), but not completely.

  1. Are you able to share the code you use for your post-processor?
  2. Is there a reason you don't build directly in Azure in the first place? I know that ISO builds are an issue, but I don't know if that is what you are doing in this case.

/cc @harijayms

@flamarion
Copy link
Author

Hi,

First of all, thank you for your quick interaction.

There is some work to size alignment indeed, but not only this.

1 - https://gist.github.com/flamarion/68aee3b5c67858cd42bc6cfe2e0e359d

2 - Yes. Due the strict regulations, the first build should be done using some ISO file, then, after created the golden image (Managed Image) , we can build directly on Azure using our previously built managed image. In other words, we can't use any image provided by Azure marketplace.

All those conversions which you're going to see on post-processor should be done in order achieve the VHD file, because only the VHD file can be converted to a managed image. I already thought in to build using directly the qemu builder, but I have no time to change all work now.

Regards,

Flamarion Jorge

@cloudbooster
Copy link
Contributor

@flamarion we are looking to create a service that you can potentially leverage for this. Do you want to connect offline so that I can understand your scenarios better

@flamarion
Copy link
Author

@harijayms Of course, let me know the best place / tool to reach you. Regards.

@flamarion
Copy link
Author

@harijayms Are you still engaged to leverage this solution? I'm willing to help with information about my scenarios and what I'm doing to push my images to Azure.

@ghost
Copy link

ghost commented Apr 30, 2021

This issue has been automatically migrated to hashicorp/packer-plugin-azure#9 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-azure#9.

@ghost ghost closed this as completed Apr 30, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants