blueprint static-datasource-configuration
- clarification on backward compatibility Change-Id: I3ee3103535760ae0415d034c640bfafdf4b4cbf3
This commit is contained in:
parent
97f3104b54
commit
ca7bfdac35
@ -78,6 +78,18 @@ evaluator template.
|
|||||||
|
|
||||||
Discover entities from the static data source template.
|
Discover entities from the static data source template.
|
||||||
|
|
||||||
|
For backward compatibility, static data source will take over the control of the
|
||||||
|
default configuration folder ``/etc/vitrage/static_datasource`` which was used
|
||||||
|
by static physical datasource.
|
||||||
|
|
||||||
|
Both legacy format and new format will be placed in the same folder. static
|
||||||
|
datasource parse the file and check the existence of ``meta`` to decide which
|
||||||
|
engine to use. If not found, proxy the job to static physical datasource and
|
||||||
|
print a deprecation warning.
|
||||||
|
|
||||||
|
Static physical datasource will be disabled by default and throws exception if
|
||||||
|
running standalone.
|
||||||
|
|
||||||
Alternatives
|
Alternatives
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user