In Usage Engine 3.0.1, there are the following known issues:
...
A workaround would be to add the 'type: string' parameter on the same level as the 'anyOf'.
The property for limiting password changes needs the property "reset.enabled" to be set
| Info |
|---|
|
Settings for the platform, values.yaml: | Code Block |
|---|
systemProperties:
- mz.security.user.control.enabled=true
- mz.security.user.password.reset.enabled=true
- mz.user.account.change.password.limit=true |
|
AWS Terraform Template does not Support M1 Mac with darwin_arm64 Architecture
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. |
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.
...