Hi David Ffrench,

In your project, we have just (string and int values). As I said it was all automatic generated and we are not adding any customized format in this PR. However, if you would like to check how it works you can :

• To test a string type

Try to apply the following file.

apiVersion: mobile-security-service.aerogear.com/v1alpha1
kind: MobileSecurityService
metadata:
  name: mobile-security-service
spec:
   routeName: 1 # It will not be applied because here is expected an string

• To test an int type

Try to apply the following file and check the validation error raised by the API/framework.

apiVersion: mobile-security-service.aerogear.com/v1alpha1
kind: MobileSecurityService
metadata:
  name: mobile-security-service
spec:
  size: "invalid because here expect an int"

• To test a customized format (the only one that we have and which is already merged in the project )

apiVersion: mobile-security-service.aerogear.com/v1alpha1
kind: MobileSecurityServiceBackup
metadata:
  name: mobile-security-service-backup
spec:
  gpgEmail: "invalid value because here expected an email"
  

However, please feel free to not do it if you do not have time at all. I am just trying to clarify how it works.