I was looking to be able to post a new topic, but I was unable to locate. The question may be somewhat relevant to this topic. I’ve noticed that when adobe@2021 is the cfengine, the updates result in the loss of previously installed packages. Is there a way to prevent the loss when the cf update occurs?
The box.json for whatever sever you want the behavior to apply to, lol. If you don’t have a box.json, you’d need to create it in the web root. Package scripts are documented here:
No. CFConfig deals with configuration read or written to/from the XML and properties files in Adobe and Lucee. Installing Lucee extensions or Adobe cfpm modules is outside the scope of just writing to an XML file. It’s an entire process of downloading and installing a jar that is dependent on Adobe’s proprietary logic baked into their cfpm CLI. CFConfig doesn’t even require a server to exist to write the config! You can literally point CFConfig to an empty directory and ask it to write out all the config XML files for an Adobe 2021 server and it will happily oblige. You can start the server the next day if you want. Given scenarios like that, it’s literally impossible for CFConfig to be dealing with something like cfpm which wouldn’t even exist.
Lucee has some much better conventions for dealing with this stuff-- deploy folders and environment variables. But Adobe only gives us the cfpm CLI which comes with a lot more assumptions about how it will be used.
Also, I recommend formatting your JSON before you paste it into a message. It will make it easier for people to understand your code and help you.
You can format your JSON using a site like: https://jsonformatter.curiousconcept.com/
Then you can paste it in here by starting with 3 backticks ``` paste your code on a new line, and then close with three backticks ```