In Usage Engine 3.0, there are the following known issues:
...
A workaround would be to add the 'type: string' parameter on the same level as the 'anyOf'.
...
title | Workaround |
---|
Settings for the platform, values.yaml:
...
.
...
Anchor awstr1 awstr1
AWS Terraform Template does not Support M1 Mac with darwin_arm64 Architecture
awstr1 | |
awstr1 |
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. |
Anchor oldDVConfig oldDVConfig
Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors
oldDVConfig | |
oldDVConfig |
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.
...
The '<agent> - 5G Support - <field>' parameters in Usage Engine 3.0
If the existing workflow contains these parameters from the older version, users are required to configure them under the new '5G Support' sub-category.
Page Properties | ||
---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9275 - Known Issue Documentation for 5G Primary & Secondary NRF Backward Compatibility in MZ9 & PE https://digitalroute.atlassian.net/browse/XE-8211 - Backward Compatibility Issue for 5G Profile & Workflow https://jira.digitalroute.com/browse/XE-4901 Mzcli - wflist - '-not-member-of-wfgroup' throws exception on baremetal https://digitalroute.atlassian.net/browse/XE-2989 - mzcli: return code improvement → not sure this is the right bug https://digitalroute.atlassian.net/browse/XE-684 - Web-UI pico details https://digitalroute.atlassian.net/browse/XE-4297 - mzonline workflow throws error when I have encrypted wfs → check when EOL of MZOnline is scheduledhttps://digitalroute.atlassian.net/browse/XE-5238 - mz.user.account.change.password.limit is not working when reset.enabled is not set → add this in user doc instead https://digitalroute.atlassian.net/browse/XE-5846 - Not possible to use terraform on a new Mac with darwin_arm64 architecture https://digitalroute.atlassian.net/browse/XE-8504 - PE Documentation contains not so relevant Properties section https://digitalroute.atlassian.net/browse/XE-4297 - mzonline workflow throws error when I have encrypted wfs https://digitalroute.atlassian.net/browse/XE-8170 - Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors https://digitalroute.atlassian.net/browse/XE-8890 - EC pod will not start if custom service account is used |
...