-
Notifications
You must be signed in to change notification settings - Fork 24
Add support for selecting storage container on image and vm disk #62
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
Comments
This feature is actually valid, as when you build the image it goes directly to the self-service storage container, an option to specify an image storage destination. Workaround is to export image locally and upload manually. |
Hello, This functionality is relatively blocking. Do you have any idea about its implementation in future features? |
I confirm this workaround is kind of blocking (you have to download/upload all your templates everytime you update them). (Another proposal should be to be able to upload to PE instead of PC from Packer, then import image from PC, it avoid the download/upload thing..) |
Yes, this is pretty important feature what is missing now. And it's also unfortunate there is no reply from any contributor. |
@Peter1295 can you explain in detail your use case and what you try to achieve thanks |
We are running Prism Central with 2 clusters, each in different datacenter (not an issue with packer, as we have set placement policy what replicate to both clusters) and have set multiple storage containers based on the location and function with separated policies. |
/kind feature
Add support for selecting storage container on image and vm disk. This option is available in the Terraform provider
The text was updated successfully, but these errors were encountered: