PROTO-1888: core plays

[alecsavvy]

Description

• adds protocol.proto to core
• adds plays/listens to the message schema
• adds a grpc server that proxies requests to the inner comet instance
• adds a ping grpc endpoint
• adds a grpc kv store endpoint
• adds multiple integration tests that pass with local stack
• adds a go script that generates functions for the "options" pattern which makes construction of structs clearer

Because of the way go modules work, a second PR will follow this for the mediorum changes as I couldn't get go workspaces to work reliably. We may want to re-think how to organize all of the go projects so they can be built together.

How Has This Been Tested?

make test with local stack

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2ae9b2d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[endline]

is this expected after make up && make test

Summarizing 4 Failures:
  [FAIL] Plays [It] submits and reads back a play through grpc
  /private/var/orion/audius/audius-protocol/core/test/integration/plays_test.go:61
  [FAIL] KvStore [It] should set kv values on one node and read on the others
  /private/var/orion/audius/audius-protocol/core/test/integration/kv_store_test.go:27
  [FAIL] Sdk [It] connects to json rpc endpoint
  /private/var/orion/audius/audius-protocol/core/test/integration/sdk_test.go:22
  [FAIL] Network [It] should be on the same network and peer
  /private/var/orion/audius/audius-protocol/core/test/integration/network_test.go:19

[alecsavvy]

Hmm no, make test should be all passing. Do you have audius-compose up running alongside it? that's a dependency @endline

[endline]

ok, yeah that worked. unreal!!

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11648676	Triggered	Generic High Entropy Secret	a4022b6	core/infra/dev_config/discovery-one.docker.env	View secret
11648678	Triggered	Generic High Entropy Secret	a4022b6	core/infra/dev_config/content-three.docker.env	View secret
11648679	Triggered	Generic High Entropy Secret	a4022b6	core/infra/dev_config/content-two.docker.env	View secret
11648680	Triggered	Generic High Entropy Secret	a4022b6	core/infra/dev_config/content-one.docker.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}