Releases: CatalystCode/project-fortis
Releases · CatalystCode/project-fortis
Test Release
0.0.46 Ensure new build hits old build cache
Test Release
0.0.45 Pull previous image to speed up builds
Test Release
0.0.44 Derive replication factor from k8 node count
Test Release
Don't hard-code location of cognitive services Previously we were assuming that the cognitive services called in the spark jobs are always deployed in WESTUS which leads to failed calls when the resources are set up somewhere else, e.g. in EASTUS. This change passes the resource group location in which the cognitive services were created through to spark so that we can format the appropriate base URL for the services. As a tangential change, this commit also removes the ability to provide cognitive services tokens at deploy time. We already have the ability to set up new cognitive services accounts during the fortis-deploy.sh script so we might as well leverage that to ensure that the cognitive services tokens and deployment locations don't risk getting out of sync which will lead to hard to debug errors for the user. This changes also has some related benefits, e.g. making billing more straight forward since all Fortis resources will be located in the same resource group by construction.
Test Release
0.0.42 Turn up the consistency for talking to Cassandra
Test Release
Implement authentication for featureservice See https://github.com/CatalystCode/project-fortis-pipeline/issues/222
Test Release
0.0.40 Update hostnames based on docker-compose config
Test Release
Move System.err calls to logger Also: handle errors in logger
Test Release
0.0.38 Enable no default topics to be ingested on deploy
Test Release
0.0.37 Handle missing schema in install script