Learn how to deploy i2 Analyze on multiple servers. Docker containers are used for demonstration purposes, so that you can replicate the deployment on physical servers.
Describe the bug
I updated the BAG connector from 1.3 to 1.4. The connector was running without issues, but after the update i2 Analyze can't find the config.
To Reproduce
Create new package
Upload this package to i2 Analyze
Change the version to 1.4.0 of the connector-version.json
Remove the certificates from the bag-connector
Run manage-environment -t connectors
Deploy the config again
Expected behavior
The correct URL to the config in the admin console.
Screenshots
The container is running
The admin console, the BAG connector has a different URL of the config somehow.
Describe the bug I updated the BAG connector from 1.3 to 1.4. The connector was running without issues, but after the update i2 Analyze can't find the config.
To Reproduce
Expected behavior The correct URL to the config in the admin console.
Screenshots The container is running
The admin console, the BAG connector has a different URL of the config somehow.
Settings
Hardware and Software information
Additional information The link in the documentation isn't available, https://i2group.github.io/analyze-connect-node-sdk/guide/walkthrough/8-packaging-and-distribution.html. Should link to https://i2group.github.io/analyze-deployment-tooling/content/connector_config_dev.html
I copied the Dockerfile and docker-entrypoint.sh from template folder to be sure that I use the latest version.
I did not do a clean deploy yet to prevent importing the data again in the Information Store.