Manifests
The manifest for an ingestion package is a simple file that identifies relevant data model files and instance data, and nodegroup files (optional). It also specifies the model and data datagraphs. It can also reference another manifest file. All file paths are resolved relative to the location of the manifest. In this page, we provide a very brief example of how manifests can be created in a single .yaml file or split into multiple .yaml files that reference one another. For a detailed guide on manifests, look here.
As the name suggests, in a single file manifest, all the necessary information is consolidated in a single .yaml file as shown below.
In some situations, for the sake of modularity, mainfests can be split into multiple .yaml files that reference each other as shown below. Here, the root-level manifest is the manifest.yaml file which references the arcos.yaml, which in turn references the rack.yaml file. The non-root-level .yaml files can take any name, but the filenames should be unique.
Go back to Wiki Home
Copyright (c) 2021-2023 General Electric Company, Galois, Inc.
All Rights Reserved
This material is based upon work supported by the Defense Advanced Research Projects Agency (DARPA) under Contract No. FA8750-20-C-0203.
Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the Defense Advanced Research Projects Agency (DARPA).
Distribution Statement "A" (Approved for Public Release, Distribution Unlimited)