will commandbox cfconfig work with CF2023?
# box-products
t
will commandbox cfconfig work with CF2023?
b
It should
t
thanks, will give it a shot shortly then
b
I don't think I added anything to CFConfig specific to 2023, but all the config that worked in previous versions should work in 2023 so far as I know
t
getting this in 2016
i wonder if we just touch that .xml file that is missing (not sure why it's missing)
b
Yeah, that's a bug
I need to override those methods in the older providers to be a no-op
t
ok, if we just touch a blank xml file that should resolve it?
b
Oh, seems I already accounted for that
Copy code
if( getSupportsMultiCloud() ) {
			readCloudCred();
			readSAML();
			readCloudConfig();
		}
t
we'll try that
b
Not sure why that's not working
Only the 2021 and 2023 providers have
Copy code
setSupportsMultiCloud( true );
So if that code is running on a 2016 server, you've got something funky going on
What is the exact command you are using?
Are you trying to force CFConfig to read 2016 config as a 2023 format or something?
t
just dumping it to JSON
then going to import it to the 2023
or maybe he's onto the second step already
the one weird thing with the enviro is we have no internet access
we got by it by installing blank xml files with <xml></xml> tags
b
What is the output of
Copy code
server info
and
Copy code
server list --local
t
came back with nothing, these are non-commandbox installations we are targetting
we're just using the tool to backup the config and restore
b
Lol, well that's not gonna work like that
That's not the right command
well, nevermind-- maybe it would work
depends on what is in the cfusion folder I guess
The fact that it's at the root of your drive tells me it's prolly not a complete CF installation
CFConfig looks at a handful of files to detect what version of CF is in there
So if you only had some files, then the auto-detect wouldn't be able to tell
You can see there are a number of jar files, XML files, and shell scripts it looks for
as well as the parent folder name for the installation (which you don't have)
If you've stripped all the identifying parts of your CF installation, the you just need to give CFConfig a hint and it will know what version to use
Copy code
cfconfig export from=T:/cfusion fromFormat=adobe@2016 to=file.json
☝️ That was prolly your "correct" fix, but I didn't realize you were using the auto-detection stuff at first
@tattva5
t
ohhhh
interesting
nah he just mapped a network drive to that folder
maybe that was the problem
was supposed to be mapped to the cfusion folder at a minimum
b
Well, you can look through that logic to see wher it failed, but I'm guessing there were files not visible to CFConfig so it just defaulted to the latest format
t
definitely user error then
I'll let him know