You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
After discussing on slack, it appears image_size_in_gb's behaviour has changed with the release of unified snapshots..
Would it be possible to update de docs to clarify how this parameter works.
Right now here are the questions I have a hard time answering:
Is it a fixed size the image will take, or just a maximum ?
How does this parameter influences the type of OS disk that is used (local vs block storage) ?
Use Case(s)
Improve shutdown time and overall packer build times
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
After discussing on slack, it appears
image_size_in_gb
's behaviour has changed with the release of unified snapshots..Would it be possible to update de docs to clarify how this parameter works.
Right now here are the questions I have a hard time answering:
Use Case(s)
Improve shutdown time and overall packer build times
Potential References
https://scaleway-community.slack.com/archives/C03B4GW7DFG/p1685450458343039
The text was updated successfully, but these errors were encountered: