Darren Bolduc

Results 114 issues of Darren Bolduc

Our build scripts have a way to support transition[^1] libraries, but as @coryan points out in https://github.com/googleapis/google-cloud-cpp/pull/13210#discussion_r1410817884 our generated code does not have a way to support transition services. We...

type: cleanup

Some services were added with unversioned clients. We generated versioned clients. To maintain backwards compatibility, we pointed the unversioned headers to versioned headers, and unversioned clients to versioned clients. See...

type: cleanup
next major: breaking change

Specify library name and version: **google-cloud-cpp/2.22.0** Update `google-cloud-cpp` to the latest version (v2.22.0). Remove the recipe for v2.12.0, and clean up recipe logic only relevant to v2.12.0. Tested with the...

Failed

The `BUILD.bazel` files are fairly cookie cutter. They are generated as scaffolding, then maintained by hand. Making sweeping changes across them (e.g. defining public headers) can be cumbersome. Factoring out...

type: cleanup

We could have one `ServiceCodeGenerator` per file, instead of one `ServiceCodeGenerator` per potential pairs of files. `ServiceCodeGenerator` writes files. It takes care to distinguish between headers and sources. It has...

type: cleanup
cpp: generator

- [x] User-defined metrics (`CreateTimeSeries`) - [ ] Google-defined metrics (`CreateServiceTimeSeries`)

type: feature request
samples
cpp: opentelemetry

We need to produce an idiomatic C++ API surface for https://cloud.google.com/bigquery/docs/reference/rest This is a big undertaking. It will have several subtasks, such as #13892. We will fill in the details...

type: feature request
api: bigquery

**google-cloud-cpp/2.23.0** - Add version 2.23.0 of `google-cloud-cpp`. - Remove version 2.12.0, and clean up code only relevant to 2.12.0. - Simplify handling of some legacy proto libraries from https://github.com/googleapis/google-cloud-cpp/issues/8022 -...

We are taking a hard dependency on `opentelemetry-cpp` and a soft dependency on gRPC's OTel plugin, even though both are required for metrics. It seems like we would want either...

api: storage
type: cleanup

Part of the work for #14269 I am not sure whether I should call this a `cleanup` or a `feat`. :shrug: env var changes will come later. --- ## Testing...

do not merge