Repository navigation
Supported CLI setup for Validator-to-Evidence-Set connections #295
togofishicorn
started this conversation in
Fetcher and Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We're trying to use the native Paramify CLI for setup while keeping our offering-specific configuration outside the fetcher repository.
Is there already a supported way to:
Our example is
collection_succeededandEVD-AZURE-RESOURCE-INVENTORY. Manifest-scoped sync selects zero Validators because that Evidence Set reference isn't listed in the shared definition. We also confirmed the documented behavior that existing Validators are skipped without repairing missing connections.We checked upstream revision
a7ed78b. The standalone--rootoption can select the unchanged definition, but it retains the definition's original Evidence Set list.We'd like to maintain only configuration and a workflow that invokes your CLI. Is there an existing supported approach we're missing? If this needs an upstream extension, what approach would you prefer?
All reactions