FEEDBACK: red or green dot on DO services

[isaac-mcfadyen]

In PR #6893, a red or green dot was added beside each service when deploying a DO with Wrangler.

I'm not too familiar with Wrangler internals, but it looks like the red vs. green is decided based on whether a service is in the registry.

Per some feedback on Discord, this isn't really clear to users, and in fact the random red dot can be kind of concerning given that there is no explanation on what it means or why your services are suddenly red.

I believe it was added in PR #6893:

workers-sdk/packages/wrangler/src/config/index.ts

Line 268 in ae4bfea

value += ` (defined in 🔴 ${script_name})`;

[AdiRishi]

Just wanted to clarify something here (I'm the OP on discord).
I didn't encounter this while deploying a DO with wrangler, but rather a worker with static assets (Remix website) with 3 bound JSRPC workers (not sure if that's the same as DO underneath)

  Total Upload: 3324.79 KiB / gzip: 1022.32 KiB
  Worker Startup Time: 235 ms
  Your worker has access to the following bindings:
  - KV Namespaces:
    - CACHIFIED_CACHE: 191f201005724b038b6facd2ae37e1d9
  - Services:
    - PUBLIC_DATA_SERVICE: 🔴 naamdeo-courses-api#PublicDataService
    - AUTHENTICATED_USER_SERVICE: 🔴 naamdeo-courses-api#AuthenticatedUserService
    - RESTRICTED_SERVICE: 🔴 naamdeo-courses-api#RestrictedService

[isaac-mcfadyen]

Hey @penalosa,

Thanks for PR #7039

While that's definitely a fix for non-local dev, I believe in local dev there's still no indication of what the red/green dots actually mean? Users aren't going to know about the registry, just that there's a random indicator beside their services that isn't explained anywhere that I can find.