sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f3121f0fb7
diskimage-builder/elements/manifests/README.rst

26 lines
988 B
ReStructuredText
Raw Normal View History

Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b
2015-02-07 10:30:02 +00:00
=========
manifests
=========
Standardise manifest creation and retrieval * Create a standard element to copy manifests out of the image and into the build area. * Ensure all current manifests are copied into a standard manifests directory Change-Id: I37eff5a13a14564e1adc33eb4f0144d571267617
2014-03-28 18:02:36 +00:00
Move generation of dib_[environment|args] to manifest element dib_[environment|args] manifest files are currently generated by the base element and then moved by the manifest element. This creates too many corner cases -- if you don't include the base element (we are trying to empty it ATM) you don't get the env/args saved at all; if you include base but don't include the manifest element they're saved to /etc, but if you do have the manifest element they're moved to the manifest dir. Move generation of these into the manifest element directly and update the documentation to reflect this. In practice this doesn't change things, because the "manifests" element gets pulled in via deps for most builds. Change-Id: I3f23037058137d166b29f0b70fd1a02c22c07fc8 Signed-off-by: Andreas Florath <andreas@florath.net>
2017-01-14 12:17:08 +00:00
An framework for saving manifest information generated during the
build for later inspection. Manifests are kept in the final image and
also copied to the build area post-image creation.
Standardise manifest creation and retrieval * Create a standard element to copy manifests out of the image and into the build area. * Ensure all current manifests are copied into a standard manifests directory Change-Id: I37eff5a13a14564e1adc33eb4f0144d571267617
2014-03-28 18:02:36 +00:00
Move generation of dib_[environment|args] to manifest element dib_[environment|args] manifest files are currently generated by the base element and then moved by the manifest element. This creates too many corner cases -- if you don't include the base element (we are trying to empty it ATM) you don't get the env/args saved at all; if you include base but don't include the manifest element they're saved to /etc, but if you do have the manifest element they're moved to the manifest dir. Move generation of these into the manifest element directly and update the documentation to reflect this. In practice this doesn't change things, because the "manifests" element gets pulled in via deps for most builds. Change-Id: I3f23037058137d166b29f0b70fd1a02c22c07fc8 Signed-off-by: Andreas Florath <andreas@florath.net>
2017-01-14 12:17:08 +00:00
Elements that wish to save any form of manifest should depend on this
element and can save their data to into the ``DIB_MANIFEST_IMAGE_DIR`` (
which defaults to ``/etc/dib-manifests``). Note this is created in
``extra-data.d`` rather than ``pre-install.d`` to allow the
``source-repositories`` element to make use of it
The manifests are copied to ``DIB_MANIFEST_SAVE_DIR``, which defaults
to ``${IMAGE_NAME}.d/``, resulting in the manifests being available as
``${IMAGE_NAME}.d/dib-manifests`` by default after the build.
Extra status
------------
This element will also add the files ``dib_environment`` and
``dib_arguments`` to the manifest recording the ``diskimage-builder``
specific environment (``DIB_*`` variables) and command-line arguments
respectively.
Reference in New Issue Copy Permalink