Skip to content

[chore]: Initial Unified Development Experience #274

Open

Description

@SuvabrataChowdhury

Chore Description

Currently developers need to know service specific toolings to spin up the service. This introduces unnecessary overhead of learning different toolings which the developer is not even responsible for. As Bazel has already been introduced, place such important service specific commands that a developer might need behind bazel so that every developer can simply use bazel to do common cross-service tasks.

As part of this initial implementation do the following,

  1. Put different startup scripts under bazel. Note, for now, for local development only, start the services in a profile which does not require external dependencies.
  2. Have a standard form of the command so that it's easy to remember. Like,
bazel run //service_name:start-dev
  1. Similarly unify the test commands like,
bazel test //service_name:unit-test

Benefit hypothesis

This will help developers talk the same language in-terms of tooling.

Chore importance

Medium

Additional comments

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

choreSome tasks, other than core application development, which helps the application's development.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions