#
# all commands executed will have the following environment variables
#   WORKING_DIR:
#      a temp dir, do what you want there, but don't delete stuff
#      you can use it to pass information between commands if you'd like
#      ie, your first command can write : mydata.txt
#      and your second command read $WORKING_DIR/mydata.txt
#
#   OUTPUT_FSTAB:
#      partitioning should write this file, the fstab that will eventually
#      be copied into the target OS (this may not be entirely true, but i
#      think curthooks does copy it)
#
#  TARGET_MOUNT_POINT:
#      at the end of partitioning, you should have all mounts done, ie so
#      a 'chroot' here would work.
#
#  CONFIG:
#      full path to a yaml file that contains the config that was
#      passed in to install with --cfg arguments.
#      it is fully merged in that multiple --cfg flags have been
#      rendered into a single file here.
#                      
#  OUTPUT_INTERFACES: this is /etc/network/interfaces style file that
#                     you should if you were configuring networking
#                     ie, this is for the 'network' stage what
#                     OUTPUT_FSTAB is for the partitioning stage

# Note, the 'builtin' command is
#  curtin block-meta simple
# so you will have to defined it to either null or a no-op ('true')
# so that it doesn't un-do your work.
#
# the builtin config that curtin has is viewable in curtin/commands/install.py
#   
partitioning_commands:
  builtin: true
  01_your_command_1: [do, whatever, here]
  02_your_command_2: [do, otherstuff, here]
  03_your_command_3: [mkfs, some-device, some-flags]
  04_your_command_4: [sh, -c, 'mount some-device $TARGET_MOUNT_POINT]