In 2.1.2, there are the following known issues:
...
It is recommended not to use or create an encrypted dynamic workflow as you will not able to make any changes to the workflow in the web interface.
Anchor ImpOldConfig ImpOldConfig
Importing Old Configurations with Web Services Using Keystore Requires Additional Configuration
ImpOldConfig | |
ImpOldConfig |
If you have an old webservice configuration from 8.x that uses keystore then the existing Security profile will be empty and to use a Security profile, you need to create a new one. This also applies to Diameter if it uses the Security profile.
...
When running the /wiki/spaces/DRXXE/pages/6210196 command in a containerized solution the ECD will unexpectedly terminate.
Anchor terraform terraform
terraform template does not support M1 Mac with darwin_arm64 architecture
terraform | |
terraform |
The setup files for AWS installation does not contain a provider that supports the new M1 Mac darwin_arm64 architecture.
The error is recorded as:
Code Block |
---|
➜ terraform terraform init Initializing the backend... Initializing provider plugins... Finding hashicorp/aws versions matching "~> 2.0"... ╷ │ Warning: Version constraints inside provider configuration blocks are deprecated │ │ on provider.tf line 5, in provider "aws": │ 5: version = "~> 2.0" │ │ Terraform 0.13 and earlier allowed provider version constraints inside the provider configuration block, but that is now deprecated and will be removed in a future version of │ Terraform. To silence this warning, move the provider version constraint into the required_providers block. ╵ ╷ │ Error: Incompatible provider version │ │ Provider registry.terraform.io/hashicorp/aws v2.70.1 does not have a package available for your current platform, darwin_arm64. │ │ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms │ supported. |
...
To be backward compliant in terms of performance requirements, it is not feasible to remove Netty 3 from MediationZone at this point.
Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors
If you have an old Data Veracity Collection Agent Workflow configuration from version 8.x, it is possible that validation errors about invalid Analysis Agents may occur.
Example error during import:
Code Block |
---|
The following agents returned validation errors.
Analysis_1 is invalid.
The UDR type DataVeracityUDR (DataVeracity) doesn't exist |
Example error when viewing the invalid workflow Analysis Agent configuration:
Code Block |
---|
Error: Failed to set UDR Types
Message: Unable to create UDR type description from DataVeracityUDR (DataVeracity). |
To resolve this, you will need to re-add the Data Veracity UDR for Analysis Agent input UDR Types or use the Set To Input button if applicable. After adding the appropriate Analysis UDR Types, save the workflow configuration.