invalid custom path cfconfig file is overwritten

Description

this then clobbers (overwrites) the (bad) custom cfconfig file, which ain't great, which is why i prefer copying the env var version into the default location

one typo and you lose your entire cfconfig

my preference is that a custom cfconfig is treated as static like env vars

I still think this should be fatal on startup

Environment

None

Activity

Michael Offner 18 July 2024 at 15:21

the invalid file is not lost, it simply get renamed with the prefix “buggy“, the same way as with Lucee 5 and all versions before.

i have improved the log message in this case:


if we wanna change the behaviour, please create a task ticket with detailed info how that exactly should be handled. and add it to the Lucee 6.2 epic, we do not feature changes anymore within minor releases.

Zac Spitzer 5 July 2024 at 15:12

by static, i think it should be R/O and simply imported into the default location, i.e never updated

Michael Offner 5 July 2024 at 13:51

can you please be more specific, what do you mean by “my preference is that a custom cfconfig is treated as static like env vars“. What behaviour you exactly expect?

Fixed

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Parent

Created 5 July 2024 at 09:55
Updated 19 July 2024 at 07:14
Resolved 19 July 2024 at 07:14