Skip to content

Split emulator into 2 artifacts #1257

@igorbernstein2

Description

@igorbernstein2

This was motivated by #1234

Currently the emulator artifact serves 2 purposes:

  1. it packages the golang binaries and wraps it a java process controller
  2. Provides grpc helpers to build a ManagedChannel to the emulator

These 2 purposes are currently handled by making grpc-api a provided api. This should be cleaned up by pulling out the zero dependency binary wrapper and process controller into a separate artifact and change the current artifact to have a hard dependency on grpc and the new artifact.

Metadata

Metadata

Assignees

No one assigned

    Labels

    api: bigtableIssues related to the googleapis/java-bigtable API.priority: p3Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions