Is your feature request related to a problem? Please describe.
Some users of AMIs created from this automation find the static partitioning-scheme problematic on long-lived systems or systems with specialty monitoring and/or tooling needs
Describe the solution you'd like
Add a flag that allows the passing of a partitioning-map to DiskSetup.sh (replacing or overriding the static values in its CarvLVM function. Probably want to pass the partitioning scheme as JSON-type data or possibly delimited triplets (MountLocation, VolumeName, VolumeSize).
Describe alternatives you've considered
Continue leaving storage relayout as a launch-time task for AMI owners...
Additional context
Other tooling that inherits this will need to be updated to take advantage and flag/option will need to be wholly optional so as not to break reliant tooling.
Is your feature request related to a problem? Please describe. Some users of AMIs created from this automation find the static partitioning-scheme problematic on long-lived systems or systems with specialty monitoring and/or tooling needs
Describe the solution you'd like Add a flag that allows the passing of a partitioning-map to
DiskSetup.sh(replacing or overriding the static values in its CarvLVM function. Probably want to pass the partitioning scheme as JSON-type data or possibly delimited triplets (MountLocation, VolumeName, VolumeSize).Describe alternatives you've considered Continue leaving storage relayout as a launch-time task for AMI owners...
Additional context Other tooling that inherits this will need to be updated to take advantage and flag/option will need to be wholly optional so as not to break reliant tooling.