v0.1.0-beta2
sduchesneau
released this
27 Apr 19:03
·
1082 commits
to develop
since this release
Added
- Added
apiproxy
application, with its flags - Added
--log-format
option for JSON output andlog-to-file
bool (default to true, same behavior as before) - Filtering (whitelist and blacklist) of what is indexed in Search, based on Google's Common Expression Language. See details here. Added
--search-common-action-filter-on-expr
and--search-common-action-filter-out-expr
.- NOTE: This doesn't affect what is extracted from the chain, allowing you to re-index selectively without a chain replay.
Changed
- CLI: dfuseeos init now writes dfuse.yaml with the
start
command's flags, also the array of components to start - CLI: new
{dfuse-data-dir}
replacement string in config flags, also changed default flag values --node-manager-config-dir
now./producer
(wasmanager/config
)--node-manager-data-dir
now{dfuse-data-dir}/node-manager/data
(wasmanagernode/data
)--mindreader-config-dir
now./mindreader
(wasmindreadernode/config
)--mindreader-data-dir
now{dfuse-data-dir}/mindreader/data
(wasmindreadernode/data
)- CLI: regrouped some flags:
--search-indexer-dfuse-hooks-action-name
,--search-live-dfuse-hooks-action-name
,--search-forkresolver-dfuse-hooks-action-name
fused into new--search-common-dfuse-hooks-action-name
.--search-...-mesh-publish-polling-duration
fused into new--search-common-mesh-publish-polling-duration
.- all of the
--search-mesh-...
options were renamed to--search-common-mesh-...
(previously--search-mesh-service-version
,--search-mesh-namespace
,--search-mesh-store-addr
) dashboard
: now separate metrics for mindreader vs producer nodedashboard
doesn't act as a reverse proxy anymore (apiproxy
does)dashboard
's default port is now:8081
eosq
's port is now proxied through:8080
, so use that.- App
manager
renamed tonode-manager
. All of its flags were changed from--manager-...
to--node-manager-...
Removed
- The
--search-...-indexing-restrictions-json
. This was replaced by the filtering listed above.