Skip to content

Selective gapic generation is brokenΒ #541

@sofisl

Description

@sofisl

I think the selective gapic generation isn't quite working, and in order to confirm we should add a full test that reads from an actual service config file, like this in this PR. @danieljbruce and I were trying out selective gapic with bigtable admin, and we attempted to generate a new library with this file. The outcome of the generation was that only a single method was listed internal, RestoreTableMetadata. This seems wrong since we listed a bunch of methods to be internal, but I also am not very familiar with the logic behind what gets generated or not.

Also, we had to change the settings property from node_settings to typescript_settings to get anything to produce, which is not how the service_yaml file is set up (it should be node_settings). I think this is a bug in the generator implementation.

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.size: sPull request size is small.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions