Is there any chance to disable the hash (it is actually nos a hash but a 6 chars random string) after username?
I understand the good of this but allowing in the CRD to configure that suffix length and been 0 a possible value may allow disable this.
Use case example:
I am creating some PostgresUser to be used by a Helm Chart which does not support any kind of secret inyection to env nor conectionString usage but plain POSTGRES_USERNAME env is set from plain value. Usually every single Helm Chart out there support password load from a secret but not all them support the same for username. A total predictable role name will fix this.
I am happy to work on this a push a PR but want to check with users and devs of the project if this makes any sense.
Is there any chance to disable the hash (it is actually nos a hash but a 6 chars random string) after username?
I understand the good of this but allowing in the CRD to configure that suffix length and been 0 a possible value may allow disable this.
Use case example:
I am creating some PostgresUser to be used by a Helm Chart which does not support any kind of secret inyection to env nor conectionString usage but plain POSTGRES_USERNAME env is set from plain value. Usually every single Helm Chart out there support password load from a secret but not all them support the same for username. A total predictable role name will fix this.
I am happy to work on this a push a PR but want to check with users and devs of the project if this makes any sense.