As we rapidly develop this project, we need to be careful to ensure that backwards incompatible changes are communicated to the user. A key part of this is the AWS_AIO_VERSION [1] number, which we use to track these sorts of changes. When a backwards incompatible change is made, this number should be incremented.
Currently, we don't proactively warn users when they are about to perform an operation that is likely to fail due to the CLI version not matching the Arkime Cluster version. We should warn the user and/or abort if they are about to perform a cross-version operation and provide guidance for how to revert to the correct version of the CLI.
Description
As we rapidly develop this project, we need to be careful to ensure that backwards incompatible changes are communicated to the user. A key part of this is the AWS_AIO_VERSION [1] number, which we use to track these sorts of changes. When a backwards incompatible change is made, this number should be incremented.
Currently, we don't proactively warn users when they are about to perform an operation that is likely to fail due to the CLI version not matching the Arkime Cluster version. We should warn the user and/or abort if they are about to perform a cross-version operation and provide guidance for how to revert to the correct version of the CLI.
[1] https://github.com/arkime/aws-aio/blob/main/manage_arkime/core/versioning.py#L12