The translation from JSON source data to tabular Congress data places the
limited resources of Congress developers in the way of the Congress users
having the flexibility to quickly try/use any data source and data field as
the need arises in their policy use cases. This spec is a proposal to
experiment with removing the translation step, thus retaining the source JSON
data model, as a promising way to overcome the limitation.
Change-Id: I9838e4bfb051fb8d9e1e83920e2253e1d6495ab7
There are no stein specs, so using a glob pattern to include them in the
output causes a warning which then breaks the build. Comment that
toctree out for now.
Change-Id: I97ca5dae30e59023256e6368aa98953f7cb157dd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This specification introduces a datasource driver and agents to collect
configuration files handled by the oslo-config library on the different
nodes and make them available to the congress datalog engine as a
datasource.
Change-Id: I5683a839e8fb85d7d44fd01e8800481fd2bd3fbb
Implements: blueprint configuration-files-validation
Co-Authored-By: Valentin Matton <vmatt.openstack@gmail.com>
Co-Authored-By: Pierre Crégut <pierre.cregut@orange.com>
Currently Congress specs sphinx doc build broken,
all of the rst files can't be built into html files,
so previewing the html format of specs is impossible.
Fix it so that we can review specs in human readable way.
Some format issues exist in current rst files, so fix these
at the same time so that tox py27 and docs build can pass.
Change-Id: I0dcdfb315e8314fb54d7333c2395d41ff6a0c9a6
Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This can cause docs jobs to fail if the project errors out on
warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910
Nate Johnston