Skip to content
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

Revert "chore: update o-f/api dependency to v0.17 (#2848)" #2858

Conversation

anik120
Copy link
Contributor

@anik120 anik120 commented Sep 13, 2022

This reverts commit bd97e32.

An older v0.17.0 release of operator-framework/api had the spec.RunAsRoot
field, which has now been updated to be the spec.GrpcPodConfig.SecurityContextConfig
field
. Reverting #2848 so that
the new v0.17.0 can be pulled in. See this comment for more info.

Signed-off-by: Anik Bhattacharjee anikbhattacharya93@gmail.com

Description of the change:

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 13, 2022
@dinhxuanvu
Copy link
Member

Can we include the justification/reasoning behind the revert in the commit message?

…#2848)"

This reverts commit bd97e32.

An older v0.17.0 release of operator-framework/api had the spec.RunAsRoot
field, which has [now been updated to be the spec.GrpcPodConfig.SecurityContextConfig
field](operator-framework/api#261). Reverting operator-framework#2848 so that
the new v0.17.0 can be pulled in. See [this comment](operator-framework#2848 (comment)) for more info.

Signed-off-by: Anik Bhattacharjee <anikbhattacharya93@gmail.com>
@anik120
Copy link
Contributor Author

anik120 commented Sep 13, 2022

@dinhxuanvu done.

@timflannagan
Copy link
Contributor

/approve cancel

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 13, 2022
@dinhxuanvu
Copy link
Member

Has this change made it to downstream?

@anik120
Copy link
Contributor Author

anik120 commented Sep 13, 2022

No it did not

Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

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

/approve

@openshift-ci
Copy link

openshift-ci bot commented Sep 13, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, dinhxuanvu

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 13, 2022
@tylerslaton
Copy link
Contributor

🤞🏻

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 13, 2022
@openshift-merge-robot openshift-merge-robot merged commit bfeb1e4 into operator-framework:master Sep 13, 2022
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants