For the settings of nodered, is it still
# umh-supportd
DanielH
01/16/2025, 4:18 PMFor the settings of nodered, is it still in the chart or is the configmap unaffected when upgrading? looking at the chart repo it looks like it will be overwritten with default values on every update if a config is not specified in the values. i have added a config to the values file and it deploys fine but it does not update the configmap.
j
Jermuk
01/16/2025, 4:52 PM@PaulH I think you can elaborate here, this issue is as far as I remember assigned to you
d
DanielH
01/17/2025, 11:02 AMok. so i had an indent problem. now it takes my settings but i get some error from the format. i have a setting like this:
nodered:
settings: |-
module.exports = {
uiPort: process.env.PORT || 1880,
mqttReconnectTime: 15000,
serialReconnectTime: 15000,
debugMaxLength: 1000,
httpRoot: '/nodered',
ui: { path: "ui" },
adminAuth: {
type: "credentials",
users: [
{
username: "admin",
password: "secretsuperduperstrongpassword.",
permissions: "*"
}
]
}
}
but i get error:
coalesce.go:286: warning: cannot overwrite table with non table for united-manufacturing-hub.nodered.settings (map[])
DanielH
01/17/2025, 12:57 PMThe problem as i understand it is the use of toPrettyJson which fails when we have both = and : in the string.
DanielH
01/18/2025, 5:09 AMAs of now no matter how i structure the values file it will be a large string with quotes. So to change the settings i need to do it direct in the configmap which means it will be overwritten on each chart upgrade.
DanielH
01/20/2025, 4:29 PM@PaulH @Jermuk any input here? as it looks now it is not possible to change the settings of nodered in the chart. You will have to do it direct in the configmap and it will be overwritten on each chart upgrade.
j
Jermuk
01/20/2025, 6:56 PMPaul just got sick, so maybe @Ferdinand can help here? Or @krgrsebastian / @Mateusz ?
m
Mateusz
01/20/2025, 9:04 PMYes you will have to do the changes of nodered in the configmap and these will be not persistent. I already positioned this as an issue. Not sure how early the DEV team can prioritize it.
j
Jermuk
01/21/2025, 7:38 AMWe are planning to let @Paul implement it after he finished the new tag processor
d
DanielH
01/21/2025, 8:15 AMGood. It causes some problems when loosing credential settings on each upgrade.
2 Views