Skip to content

Conversation

@steveej
Copy link
Contributor

@steveej steveej commented Feb 27, 2020

This also reorganizes the imports, common code to all plugins, and
adjusts the terminology.

Fixes #237.

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 27, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 27, 2020
@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch from 9c90cd4 to 870daa9 Compare February 27, 2020 20:19
@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 27, 2020
@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch 4 times, most recently from 295487b to bfe13cd Compare February 27, 2020 21:01
@vrutkovs
Copy link
Contributor

Requires openshift/release#7370 to pass (secret change)

@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch from bfe13cd to 20154d4 Compare February 28, 2020 21:09
@openshift-ci-robot openshift-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Feb 28, 2020
@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch from 20154d4 to c6ef825 Compare February 28, 2020 21:14
@steveej steveej removed request for lucab and pbergene March 2, 2020 15:25
@steveej
Copy link
Contributor Author

steveej commented Mar 2, 2020

@vrutkovs do you know why this happened in the cargo-test job?

 2020/02/29 01:16:33 error: unable to signal to artifacts container to terminate in pod cargo-test, triggering deletion: could not run remote command: unable to upgrade connection: container not found ("artifacts")
2020/02/29 01:16:33 error: unable to retrieve artifacts from pod cargo-test: could not read gzipped artifacts: unable to upgrade connection: container not found ("artifacts")
{"component":"entrypoint","file":"prow/entrypoint/run.g

I do expect the test itself to fail right now, but this doesn't look like the failure I expected.

@vrutkovs
Copy link
Contributor

vrutkovs commented Mar 2, 2020

/retest

Seems to be yet another CI flake

@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch 2 times, most recently from b7f91d9 to 820a9a4 Compare March 2, 2020 16:32
@steveej
Copy link
Contributor Author

steveej commented Mar 3, 2020

/retest

@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch 3 times, most recently from 72b8021 to e90cf44 Compare March 3, 2020 15:34
@steveej
Copy link
Contributor Author

steveej commented Mar 3, 2020

/test ci/prow/cargo-test

Triggering a re-test as CI should be fixed after openshift/release#7449.

@steveej
Copy link
Contributor Author

steveej commented Mar 3, 2020

Trying again.

/test cargo-test

@vrutkovs
Copy link
Contributor

vrutkovs commented Mar 4, 2020

test_get_labels wants CINCINNATI_TEST_QUAY_API_TOKEN

@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

test_get_labels wants CINCINNATI_TEST_QUAY_API_TOKEN

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:

thread 'net::private::test_wrong_auth' panicked at 'CINCINNATI_TEST_QUAY_API_TOKEN missing: NotUnicode("\xA9\xF85\u{14}

@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

/retest

@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

/test cargo-test

Copy link
Contributor

@vrutkovs vrutkovs left a 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

Copy link
Contributor

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

Copy link
Contributor Author

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?

Copy link
Contributor

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

Copy link
Contributor Author

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.

@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

/retest

@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

/test cargo-test

steveej added 6 commits March 4, 2020 12:24
…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.
@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch from 21497b9 to a818db1 Compare March 4, 2020 11:24
@steveej
Copy link
Contributor Author

steveej commented Mar 4, 2020

/test cargo-test

Copy link
Contributor

@vrutkovs vrutkovs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2020
@steveej steveej force-pushed the pr/graph-builder-make-plugins-configurable branch from bdfba2c to 0395dc0 Compare March 4, 2020 15:00
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2020
Copy link
Contributor

@vrutkovs vrutkovs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2020
@openshift-ci-robot
Copy link

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 0ea6690 into openshift:master Mar 4, 2020
@steveej steveej deleted the pr/graph-builder-make-plugins-configurable branch September 25, 2020 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Example run for graph-builder errors out

4 participants