Admit "<cluster>" when parsing ResourceIDs
The PR #1442 introduce code to determine which namespace, if any, each manifest belongs to. To distinguish between resources that need a namespace but don't have one, and resources that are cluster-scoped, it introduced the sentinel value `<cluster>` for the latter. Regrettably, I didn't accompany this with code for _parsing_ those sentinel values, since I reasoned that it would only be used internally. But the sync events generated by fluxd include a list of changed resources, and those inevitably will include things like namespaces that are cluster-scoped. The result is that fluxd will generate events that cannot then be parsed by the receiver. This commit fixes that by recognising `<cluster>` as a namespace when parsing resource IDs.
|1 year ago|
Allow colons in the name component of resource IDs
There are published manifests that people want to be use with flux, but use colons in resource names. Kubernetes admits these, so we may as well too.
|2 years ago|