Expand the character set allowed in label keys and values [163555524]

Assigned

Feature Request

Status Update

No update yet.

Description

ja...@sky.uk

created issue #1

Aug 12, 2020 03:54PM

Currently, the set of characters that can be used for labels (keys and values) is extremely limited. You are currently only allowed to use:

- Lowercase letters
- Numbers
- Underscores
- Dashes

This is an extremely limited character set. Other public clouds do not have these restrictions and it doesn't seem clear why GCP does?

Can the character set available for use within labels be expanded dramatically to support a much wider range of characters?

@ and . are the two most obvious examples as we regularly use email addresses in our tagging strategy within AWS and Azure and not being able to do so within GCP is extremely restrictive.

Comments

md...@google.com <md...@google.com> #2Aug 12, 2020 08:57PM

Status: Won't Fix (Infeasible)

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

ja...@sky.uk <ja...@sky.uk> #3Aug 12, 2020 09:17PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

ma...@google.com <ma...@google.com> #4Aug 13, 2020 11:20AM

Status: Assigned (reopened)

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

Issue 163555524

Description

Issue summary

Comments

md...@google.com <md...@google.com> #2Aug 12, 2020 08:57PM

ja...@sky.uk <ja...@sky.uk> #3Aug 12, 2020 09:17PM

ma...@google.com <ma...@google.com> #4Aug 13, 2020 11:20AM

Add comment

Issue metadata