I recognize the following situation is somewhat unique, but bear with me.
Between 1.11.x and v 2.0, the SFTP variables in bricolage.conf changed. Initially, I didn't notice it, but in debugging my SSH issues (which you can see on the user list), I found that I needed to replace the old config variables with the new. All the other files had all updated properly.
It got me wondering if this is an issue other users might run into when upgrading. It seems like 99% of the time, not touching the config file during an upgrade is the proper thing to happen. Given, though, that we keep dumping switches into the config file, I wonder if that's really how it should go. I say this not having done an upgrade from 1.10 to 2 for a *long* time, so I don't know how that gets handled.
If this is something only bleeding edge developers like myself (haha) run into, then I'm willing to accept some pain. But my worry is that something similar will happen for normal upgrades, in which case we might want to do change how it's being done.
-Matt
Between 1.11.x and v 2.0, the SFTP variables in bricolage.conf changed. Initially, I didn't notice it, but in debugging my SSH issues (which you can see on the user list), I found that I needed to replace the old config variables with the new. All the other files had all updated properly.
It got me wondering if this is an issue other users might run into when upgrading. It seems like 99% of the time, not touching the config file during an upgrade is the proper thing to happen. Given, though, that we keep dumping switches into the config file, I wonder if that's really how it should go. I say this not having done an upgrade from 1.10 to 2 for a *long* time, so I don't know how that gets handled.
If this is something only bleeding edge developers like myself (haha) run into, then I'm willing to accept some pain. But my worry is that something similar will happen for normal upgrades, in which case we might want to do change how it's being done.
-Matt