-
Notifications
You must be signed in to change notification settings - Fork 60
graph-builder: move plugins to cincinnati crate and catalog, and make plugins configurable #234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
graph-builder: move plugins to cincinnati crate and catalog, and make plugins configurable #234
Conversation
9c90cd4 to
870daa9
Compare
295487b to
bfe13cd
Compare
|
Requires openshift/release#7370 to pass (secret change) |
bfe13cd to
20154d4
Compare
20154d4 to
c6ef825
Compare
|
@vrutkovs do you know why this happened in the I do expect the test itself to fail right now, but this doesn't look like the failure I expected. |
|
/retest Seems to be yet another CI flake |
b7f91d9 to
820a9a4
Compare
|
/retest |
72b8021 to
e90cf44
Compare
|
/test ci/prow/cargo-test Triggering a re-test as CI should be fixed after openshift/release#7449. |
|
Trying again. /test cargo-test |
|
|
The secret exists since there is no error around after reading them at https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cincinnati/234/pull-ci-openshift-cincinnati-master-cargo-test/974#1:build-log.txt%3A15, but it's decipherable by the test: |
|
/retest |
|
/test cargo-test |
vrutkovs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor notes, looks good otherwise
...ati/src/plugins/internal/graph_builder/github_openshift_secondary_metadata_scraper/plugin.rs
Outdated
Show resolved
Hide resolved
graph-builder/src/config/file.rs
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are currently no requirements for Cincinnati releases (there aren't any really :) ). Do we want to keep it? I think its safe to remove it now, while we control the template and no disconnected installs are in the wild
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will be very happy to remove it ASAP, but I'm hesitant to add the change to this PR. How about a separate ticket for rethinking the options?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have more deprecated options to remove though? I don't mind removing these later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to remove all UpstreamOptions but I didn't want to touch all of them in this PR. I touched this one now because it's not in the correct place. I added this option to the ServiceOptions.
|
/retest |
|
/test cargo-test |
…configurable The primary goal of this change is to make the graph-builder plugins configurable via a config file. This required all of the configurable plugins to be in the plugin catalog, which lives in the cincinnati crate. Therefore all graph-builder plugins are moved to the cincinnati crate, leaving the graph-builder crate with only its core functionality. Subsequently the graph-builder is made configurable, with a few refactors along the way as they fit in naturally with this change: * and the naming of the related functions and variable names in the graph-builder and policy-engine are normalized. * the yaml_lint
…_path This tolerates the empty string credentials_path when deserializing the the plugin settings. This is to alleviate some difficulties with deployment tools, where it is sometimes easier to set an empty than avoiding to set it.
This moves the `pause-secs` setting from the upstream.registry to the service options, because the pause occurs in the core service loop, and is not specific to any upstream method or plugin.
…usize This makes the fetch_concurrency setting an integer in the TOML configuration files instead of a String. This seems more intuitive to me from a user perspective, as I wouldn't surround an integer number with quotes intuitively.
* Rename the secret to a recent secret rename. * Create dummy secret in e2e job as the real secrets are unavailable here.
21497b9 to
a818db1
Compare
|
/test cargo-test |
vrutkovs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
bdfba2c to
0395dc0
Compare
vrutkovs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: steveeJ, vrutkovs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This also reorganizes the imports, common code to all plugins, and
adjusts the terminology.
Fixes #237.