search

TIBCOSoftware / be-tools

Collection of tools to work with TIBCO BusinessEvents
https://www.tibco.com/products/tibco-businessevents
Other
9 stars 4 forks source link

Helm release deployment fails when RMS env section has integer type GV's #207

Closed AdittyThakare closed 3 years ago

AdittyThakare commented 3 years ago

Helm installation fails when RMS section has integer global variables in values.yaml file. Tested with RMS+ Mysql DB and GV's are specified as follows: Webstudio_gv_DB_gv_driverName: com.mysql.jdbc.Driver Webstudio_gv_DB_gv_url: jdbc:mysql://mysql-0.mysql.default.svc.cluster.local:3306/BE_DATABASE Webstudio_gv_DB_gv_maxConnections: 5 Webstudio_gv_DB_gv_userName: BE_USER Webstudio_gv_DB_gv_password: BE_USER Webstudio_gv_DB_gv_timeout: 0

As Webstudio_gv_DB_gv_maxConnections and Webstudio_gv_DB_gv_timeout are integer type global variables, helm installation fails with following error: C:\RMS_Helm\be-tools-feature-rms-helm\cloud\kubernetes>helm install ignite-mysql ./helm Error: StatefulSet in version "v1" cannot be handled as a StatefulSet: v1.StatefulSet.Spec: v1.StatefulSetSpec.Template: v1.PodTemplateSpec.Spec: v1.PodSpec.Containers: []v1.Container: v1.Container.Env: []v1.EnvVar: v1.EnvVar.v1.EnvVar.Value: ReadString: expects " or n, but found 5, error found in #10 byte of ...|,"value":5},{"name":|..., bigger context ...|ame":"Webstudio_gv_DB_gv_maxConnections","value":5},{"name":"Webstudio_gv_DB_gv_password","value":"B|...

After removing the integer GV's from values.yaml helm installation work fine.

LakshmiMekala commented 3 years ago

fixed issue, changes available in PR #194

AdittyThakare commented 3 years ago

Agree fixed. Helm deployment works fine for integer GV values. Verified with ' Webstudio_gv_DB_gv_timeout: 30 ' property under RMS environment.