Skip to content

Commit 2898b1b

Browse files
author
cloud-team-rebase-bot
committed
UPSTREAM: <drop>: Updating and vendoring go modules after an upstream rebase
1 parent ccdd96a commit 2898b1b

4,859 files changed

Lines changed: 594437 additions & 334336 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎go.mod‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
module cloud.ibm.com/cloud-provider-ibm
22

3-
go 1.22
3+
go 1.25.7
44

55
require (
66
github.com/IBM/go-sdk-core/v5 v5.21.2

‎vendor/cel.dev/expr/.bazelversion‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
7.3.2
2+
# Keep this pinned version in parity with cel-go

‎vendor/cel.dev/expr/.gitattributes‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
*.pb.go linguist-generated=true
2+
*.pb.go -diff -merge

‎vendor/cel.dev/expr/.gitignore‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
bazel-*
2+
MODULE.bazel.lock

‎vendor/cel.dev/expr/BUILD.bazel‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
load("@io_bazel_rules_go//go:def.bzl", "go_library")
2+
3+
package(default_visibility = ["//visibility:public"])
4+
5+
licenses(["notice"]) # Apache 2.0
6+
7+
go_library(
8+
name = "expr",
9+
srcs = [
10+
"checked.pb.go",
11+
"eval.pb.go",
12+
"explain.pb.go",
13+
"syntax.pb.go",
14+
"value.pb.go",
15+
],
16+
importpath = "cel.dev/expr",
17+
visibility = ["//visibility:public"],
18+
deps = [
19+
"@org_golang_google_protobuf//reflect/protoreflect",
20+
"@org_golang_google_protobuf//runtime/protoimpl",
21+
"@org_golang_google_protobuf//types/known/anypb",
22+
"@org_golang_google_protobuf//types/known/durationpb",
23+
"@org_golang_google_protobuf//types/known/emptypb",
24+
"@org_golang_google_protobuf//types/known/structpb",
25+
"@org_golang_google_protobuf//types/known/timestamppb",
26+
],
27+
)
28+
29+
alias(
30+
name = "go_default_library",
31+
actual = ":expr",
32+
visibility = ["//visibility:public"],
33+
)

‎vendor/cel.dev/expr/CODE_OF_CONDUCT.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Contributor Code of Conduct
2+
## Version 0.1.1 (adapted from 0.3b-angular)
3+
4+
As contributors and maintainers of the Common Expression Language
5+
(CEL) project, we pledge to respect everyone who contributes by
6+
posting issues, updating documentation, submitting pull requests,
7+
providing feedback in comments, and any other activities.
8+
9+
Communication through any of CEL's channels (GitHub, Gitter, IRC,
10+
mailing lists, Google+, Twitter, etc.) must be constructive and never
11+
resort to personal attacks, trolling, public or private harassment,
12+
insults, or other unprofessional conduct.
13+
14+
We promise to extend courtesy and respect to everyone involved in this
15+
project regardless of gender, gender identity, sexual orientation,
16+
disability, age, race, ethnicity, religion, or level of experience. We
17+
expect anyone contributing to the project to do the same.
18+
19+
If any member of the community violates this code of conduct, the
20+
maintainers of the CEL project may take action, removing issues,
21+
comments, and PRs or blocking accounts as deemed appropriate.
22+
23+
If you are subject to or witness unacceptable behavior, or have any
24+
other concerns, please email us at
25+
[cel-conduct@google.com](mailto:cel-conduct@google.com).

‎vendor/cel.dev/expr/CONTRIBUTING.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# How to Contribute
2+
3+
We'd love to accept your patches and contributions to this project. There are a
4+
few guidelines you need to follow.
5+
6+
## Contributor License Agreement
7+
8+
Contributions to this project must be accompanied by a Contributor License
9+
Agreement. You (or your employer) retain the copyright to your contribution,
10+
this simply gives us permission to use and redistribute your contributions as
11+
part of the project. Head over to <https://cla.developers.google.com/> to see
12+
your current agreements on file or to sign a new one.
13+
14+
You generally only need to submit a CLA once, so if you've already submitted one
15+
(even if it was for a different project), you probably don't need to do it
16+
again.
17+
18+
## Code reviews
19+
20+
All submissions, including submissions by project members, require review. We
21+
use GitHub pull requests for this purpose. Consult
22+
[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23+
information on using pull requests.
24+
25+
## What to expect from maintainers
26+
27+
Expect maintainers to respond to new issues or pull requests within a week.
28+
For outstanding and ongoing issues and particularly for long-running
29+
pull requests, expect the maintainers to review within a week of a
30+
contributor asking for a new review. There is no commitment to resolution --
31+
merging or closing a pull request, or fixing or closing an issue -- because some
32+
issues will require more discussion than others.

‎vendor/cel.dev/expr/GOVERNANCE.md‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Project Governance
2+
3+
This document defines the governance process for the CEL language. CEL is
4+
Google-developed, but openly governed. Major contributors to the CEL
5+
specification and its corresponding implementations constitute the CEL
6+
Language Council. New members may be added by a unanimous vote of the
7+
Council.
8+
9+
The MAINTAINERS.md file lists the members of the CEL Language Council, and
10+
unofficially indicates the "areas of expertise" of each member with respect
11+
to the publicly available CEL repos.
12+
13+
## Code Changes
14+
15+
Code changes must follow the standard pull request (PR) model documented in the
16+
CONTRIBUTING.md for each CEL repo. All fixes and features must be reviewed by a
17+
maintainer. The maintainer reserves the right to request that any feature
18+
request (FR) or PR be reviewed by the language council.
19+
20+
## Syntax and Semantic Changes
21+
22+
Syntactic and semantic changes must be reviewed by the CEL Language Council.
23+
Maintainers may also request language council review at their discretion.
24+
25+
The review process is as follows:
26+
27+
- Create a Feature Request in the CEL-Spec repo. The feature description will
28+
serve as an abstract for the detailed design document.
29+
- Co-develop a design document with the Language Council.
30+
- Once the proposer gives the design document approval, the document will be
31+
linked to the FR in the CEL-Spec repo and opened for comments to members of
32+
the cel-lang-discuss@googlegroups.com.
33+
- The Language Council will review the design doc at the next council meeting
34+
(once every three weeks) and the council decision included in the document.
35+
36+
If the proposal is approved, the spec will be updated by a maintainer (if
37+
applicable) and a rationale will be included in the CEL-Spec wiki to ensure
38+
future developers may follow CEL's growth and direction over time.
39+
40+
Approved proposals may be implemented by the proposer or by the maintainers as
41+
the parties see fit. At the discretion of the maintainer, changes from the
42+
approved design are permitted during implementation if they improve the user
43+
experience and clarity of the feature.

vendor/github.com/google/gofuzz/LICENSE renamed to vendor/cel.dev/expr/LICENSE

File renamed without changes.

‎vendor/cel.dev/expr/MAINTAINERS.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# CEL Language Council
2+
3+
| Name | Company | Area of Expertise |
4+
|-----------------|--------------|-------------------|
5+
| Alfred Fuller | Facebook | cel-cpp, cel-spec |
6+
| Jim Larson | Google | cel-go, cel-spec |
7+
| Matthais Blume | Google | cel-spec |
8+
| Tristan Swadell | Google | cel-go, cel-spec |
9+
10+
## Emeritus
11+
12+
* Sanjay Ghemawat (Google)
13+
* Wolfgang Grieskamp (Facebook)

0 commit comments

Comments
 (0)