handle token id and secret in case of pure integer values

[JensAc]

No description provided.

[JensAc]

In case the token id or secret for the pre-gardenlet chart is a pure integer number, the deployment of the gardenlet fails.
This should be handled somehow.

[JensAc]

Moreover, the secret id has to be 6 characters long and the length of the secret has to be 16 characters.
This should be checked somewhere.

[fynluk]

Isn't it solved by #202:

export TOKEN_ID=ab$(openssl rand -hex 2)
export TOKEN_SECRET=cd$(openssl rand -hex 7)

The ab/cd prefix prevents pure int numbers

[JensAc]

That prevents it in the ci scripts. However, in "real" environments that does not prevent the user to use a pure integer token.

[fynluk]

A solution could be to limit the values file like I did here: gardener-community/pre-gardenlet@242326a

With a json-schema (https://json-schema.org/draft/2020-12/json-schema-validation.html) you can validate value files