Skip to content

Updown sync #260

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

Closed
wants to merge 117 commits into from
Closed

Updown sync #260

wants to merge 117 commits into from

Conversation

perdasilva
Copy link
Contributor

@perdasilva perdasilva commented Mar 4, 2022

Syncing upstream changes from api/operator-registry/operator-lifecycle-manager to the downstream

@openshift-ci openshift-ci bot requested review from exdx and joelanford March 4, 2022 09:43
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. labels Mar 4, 2022
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 4, 2022
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 4, 2022
@perdasilva
Copy link
Contributor Author

/verify-owners

@openshift-ci openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 4, 2022
@perdasilva
Copy link
Contributor Author

/hold need to merge #261 then rebase

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2022
@perdasilva
Copy link
Contributor Author

/retest

2 similar comments
@perdasilva
Copy link
Contributor Author

/retest

@perdasilva
Copy link
Contributor Author

/retest

@perdasilva perdasilva force-pushed the updown_sync branch 3 times, most recently from 18c4dce to 048c75a Compare March 7, 2022 15:38
joelanford and others added 10 commits March 9, 2022 16:41
…thub/workflows/release.yaml

Signed-off-by: Joe Lanford <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: a629d38a2273aa0cd43b7f06702c8c631401f30c
Upstream-repository: operator-registry
Upstream-commit: 3c2677ea67da9bb96d9f1db9e45dd4e46b81dd8e
This PR bumps operator-framework/api to v0.11.0

Signed-off-by: Anik Bhattacharjee <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: acaac87c522f1826dce8669eb9108ccacc73af75
In PR openshift#888, there's vendoring of the cel-go package, one of which
is named "debug" (github.com/google/cel-go/common/debug). Due to
the .gitignore file ignoring all [Dd]bug folders, the vendored
package isn't being checked in by git, causing the build to fail.
This PR removes the instruction to ignore [Dd]bug/ folders.

Signed-off-by: Anik Bhattacharjee <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 7a09b48dba29e8d063916f276740a1d737b40121
Updating for reader experience.

Signed-off-by: Shivkumar13 <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 611525be3bd7374d1e55d43c519e5664e0e91c2c
This commit bumps operator-framework/operator-registry requirement
go-sqlite3 from v1.10.0 to v1.14.10

Signed-off-by: Noah Sapse <[email protected]>

Co-authored-by: Noah Sapse <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 4e3865a5cf1a2b1048d3752071ae1e932953f29c
This commit introduces a series of unit tests
that ensure that GRPC connections are configurable
through the use of the GRPC_PROXY environment
variable.

Signed-off-by: Alexander Greene <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: a68dc4262ccb41cc6031ab4ef3823f6ce1713036
…r init hooks (#2523)

Signed-off-by: Per G. da Silva <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: b414e6e881066115b4c5dc63840e8d47c624a405
Prepend the https://github.com to ensure that markdown rendered links
are not resolved as local links.

Signed-off-by: timflannagan <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: bfe8f0f5339c03c4f1ac08ca343b0a5ab28a787a
…(#2463)

Update any relevant workflows and downgrade the checkouts action from
the v2 to v1 version. This change is predicated on the problematic
checkouts@v2 behavior that can lead to an increased change of regressing
when landing changes to the default branch (e.g. master/main). This is
because there's an existing bug in the v2 world where PRs can checkout
the wrong HEAD commit, leading to scenarios where you're testing against
an out-of-date commit compared to what's in the master branch.

A concrete use case is when a PR is opened, and that PR checks out the
current HEAD commit from master, and then a change lands in the master
branch, and any subsequent workflow retries for that PR will result in
that previous HEAD commit being checked out. There are workarounds that
exist, like rebasing the existing PR, or like explicitly pointing the
ref to the default branch, but this interaction isn't ideal with workflows
are triggered on pushes to branches on top of reacting to pull request
triggers. The simplest solution is to revert back to the v1 version and
find a better longer term solution.

Signed-off-by: timflannagan <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: a2142c1c3b38bd7f0d2a6fb57d6ffdf5e5434604
jpower432 and others added 18 commits March 9, 2022 16:41
…ift#897)

* feat(registry): add podman auth.json as an alternate location

Adds podman default credential location as an alternate location
when loading the config for containerd registry resolver

Signed-off-by: Jennifer Power <[email protected]>

* fix: remove named return values in resolver and add xdg library for cross-platform option

Signed-off-by: Jennifer Power <[email protected]>

* fix: update go.sum for with new xdg import

Signed-off-by: Jennifer Power <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: c056ac1f075b38031263893758fcfe6c96dcee79
Move the `opm alpha generate` command up to `opm generate`

Signed-off-by: kevinrizza <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: d69d2e41d74c16806fbc7b1ebd516ea6723f04f8
Upstream-repository: operator-registry
Upstream-commit: 3fa02bc295358a6e3259a1da11bfa35c89e58898
…Only mode (openshift#905)

opm diff in headsOnly mode with an include config will prune all empty channels
from a package which can leave the output config with an empty package. This change
will remove any empty packages after the channel pruning.

Fixes openshift#904

Signed-off-by: Jennifer Power <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: f7e27734f3a633ec03e55779317dd1af4d2cfd0a
…fy (openshift#898)

* fix(registry): deprecated skip-tls and add use-http and skip-tls-verify

The skip-tls flag currently uses HTTP instead of the expected behavior of skipping
TLS cert validated with HTTPS registries. The new flags seperate untrusted HTTPS from
HTTP registries and behave as expected

Signed-off-by: Jennifer Power <[email protected]>

* chore: add helper function to validate and get TLS options for opm command

Signed-off-by: Jennifer Power <[email protected]>

* chore: add warning message for plain HTTP in registy add command

Signed-off-by: Jennifer Power <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 354cd385167844295a3288b5a8e7fb5efb9e652b
…onfigs (openshift#914)

Signed-off-by: Joe Lanford <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 0b008deff332346247624ccc54df64b75cfe9777
…ontents (openshift#915)

Signed-off-by: Joe Lanford <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 7827c48d1a09fe320af46afe5e19491784b7f89e
Signed-off-by: Ankita Thomas <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: d59081db05ae040ebacf74f3ccfefd3bbdd9cdca
Signed-off-by: akihikokuroda <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 5566e4b6832a7fc08c12d3c79fc0a0b8c6a2e7aa
* Upgrade github.com/docker/cli to v20.10.12

Signed-off-by: Jan Boehm <[email protected]>

* Synchronize docker config loading

This prevents data races during testing. The root cause
are unsecured globals in the docker cli lib.

Signed-off-by: Jan Boehm <[email protected]>

* Mention upstream issue that fixes the data race

Signed-off-by: Jan Boehm <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: c496cf028568091b18633a9ee59dadcc6d4b4edb
This commit updates the operator-registry's go version
to v1.17.

Signed-off-by: Alexander Greene <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: c970d617ce2d77c096102e2d881a15ef680bacf9
Signed-off-by: akihikokuroda <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 5c3f4a3a3365c6684f78a3617e4cfc650bec73e3
…#908 (openshift#909)

Signed-off-by: Ryan Emerson <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 9999f79682d0073bf9ed5edf2cca1476abf2fc9a
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 9, 2022

@perdasilva: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify acd4a04 link true /test verify
ci/prow/e2e-aws-olm acd4a04 link true /test e2e-aws-olm
ci/prow/unit-api acd4a04 link true /test unit-api
ci/prow/e2e-upgrade acd4a04 link true /test e2e-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@perdasilva perdasilva closed this Mar 12, 2022
awgreene pushed a commit to awgreene/operator-framework-olm that referenced this pull request Dec 14, 2022
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
perdasilva pushed a commit to perdasilva/operator-framework-olm that referenced this pull request Mar 7, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Mar 15, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Mar 28, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Apr 6, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request May 23, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Jul 11, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Jul 17, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
tmshort pushed a commit to tmshort/operator-framework-olm that referenced this pull request Jul 20, 2023
updated

format

defs

Upstream-repository: api
Upstream-commit: ff2dbc53d3817df9b62a83dbe83cb221e7c043f4
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
Projects
None yet
Development

Successfully merging this pull request may close these issues.