Hi, Tyler. I just double-checked to confirm, the gpii-couchdb-test-harness used in testing universal is not pinned to a specific version, so it just pulls the latest couchdb docker image. 2.3 was published in February, so we've already been testing with 2.3 for a while in CI in environment that can directly use docker.
We install CouchDB within Windows VMs using an installer, and the provisioning script used in windows tests is pinned to 2.3.0 <https://github.com/GPII/windows/blob/master/provisioning/CouchDB.ps1#L53>. The gpii-app repo reuses the provisioning script from the windows repo <https://github.com/GPII/gpii-app/blob/master/provisioning/Build.ps1#L46>, so it looks to me like our core projects that use CouchDB are already tested with 2.3.0. Cheers, Tony On Tue, 23 Apr 2019 at 05:29, Tyler Roscoe <[email protected]> wrote: > As mentioned in the last Architecture Weekly, we need to upgrade couchdb > to 2.3 for security patches: https://issues.gpii.net/browse/GPII-3846 > > The only place I could find (outside of gpii-infra) that references a > couchdb version is in universal, where it uses latest (which means that > universal CI has been using the new couchdb since it was released): > https://github.com/GPII/universal/blob/master/scripts/vagrantCloudBasedContainers.sh#L31 > > Does anyone know of other areas that need to be updated? > > Ops will perform the couchdb upgrade in production at our convenience. We > believe the upgrade is low risk and will cause minimal downtime (on the > order of seconds). However, let us know if you have any concerns. > > Thanks, > t > _______________________________________________ > Architecture mailing list > [email protected] > https://lists.gpii.net/mailman/listinfo/architecture >
_______________________________________________ Architecture mailing list [email protected] https://lists.gpii.net/mailman/listinfo/architecture
