docs/architecture/object-mapper.md

129 - param: associationPath - the path to look for the association endpoints.
178 # All output must be in the association endpoints
181   xyz.openbmc_project.Association endpoints
207 - param: association - The endpoint association.
218 ASSOCIATION="powered_by"
225 string:"${ASSOCIATION}" \
260 # All output must be in the association endpoints that ends with the given `id`
263    /xyz/openbmc_project/inventory/system/chassis/${ASSOCIATION} \
264   xyz.openbmc_project.Association endpoints
315 - param: associationPath - the path to look for the association endpoints.
339 # All output must be in the association endpoints
342   xyz.openbmc_project.Association endpoints
364 - param: association - The endpoint association.
375 ASSOCIATION="powered_by"
382 string:"${ASSOCIATION}" \
392 # All output must be in the association endpoints that ends with the given `id`
395    /xyz/openbmc_project/inventory/system/chassis/${ASSOCIATION} \
396   xyz.openbmc_project.Association endpoints
476 `xyz.openbmc_project.Association.Definitions` interface, and then when an
477 association is desired, the `Associations` property on that interface needs to
486 - forward: this is the name of the forward association object
487 - reverse: this is the name of the reverse association object
502 On each of these objects, the interface `xyz.openbmc_project.Association` will
504 array that holds the object paths to the other end of the association.
509 If another object, say `pathC`, also has an association to `pathB`, then a
517 the mapper will remove the 2 association paths until `pathB` shows back up
520 Note: The original name of the association definition interface was
541 # Newly created forward association object
548 # Newly created reverse association object