You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, i am working on this issue , i just need some clarification
Could you please provide more details on what "reserving" labels with "pebble-" prefix entails? Are we preventing users from creating such labels? Or is it about some internal logic?
Scope: Is the reservation of "pebble-" prefixed labels only applicable to certain parts of the Pebble system, or is it universally across all features?
Case Sensitivity: Is the "pebble-" prefix case-sensitive? Should I treat "Pebble-" the same as "pebble-" when implementing this feature?
Hi @aliamerj, reserving the label means the user shouldn't be able to create a layer with that label. i.e. label names of the form nnn-pebble-* are disallowed.
There is currently code in the plan package which checks for e.g. reserved service names - just add a check for reserved labels, and a corresponding unit test.
I think just handle the lowercase version pebble-, don't worry about other cases.
Following the discussions from #191 (comment), consider making any layer labels starting with the
pebble-
prefix reserved.The text was updated successfully, but these errors were encountered: