Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Fix ResourceIDRegexp to allow dots in resource names #1199

Closed

Conversation

oliviabarrick
Copy link
Contributor

Some resources (particularly CustomResourceDefinitions) have dots in their names, these
are currently considered invalid by ResourceIDRegexp.

I do not know if this causes an issue inside of Flux, but I import it for fluxcloud and
it breaks unmarshalling events:

error decoding: parsing default:customresourcedefinition/clustersecrets.clustersecret.codesink.net: invalid service ID

Some resources (particularly CustomResourceDefinitions) have dots in their names, these
are currently considered invalid by ResourceIDRegexp.

I do not know if this causes an issue inside of Flux, but I import it for fluxcloud and
it breaks unmarshalling events:

```
error decoding: parsing default:customresourcedefinition/clustersecrets.clustersecret.codesink.net: invalid service ID
```
@squaremo
Copy link
Member

squaremo commented Jul 4, 2018

Beat you to it, just, in #1197.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants