Red Hat Ansible Automation Platform on Azure Unsupported Deployment Parameters

Updated

Microsoft Azure supports a number of ways to interact with its interfaces in order to deploy resources, including managed applications like Red Hat Ansible Automation Platform on Microsoft Azure. Red Hat recommends using the Azure console to configure and deploy the solution because the UI has deployment validation that is not present when using APIs or declarative tools like Azure ARM, Bicep, or TerraForm to deploy the managed application.

If you choose to use a deployment model outsize of the Azure console, then there are parameters that are exposed that you should not edit as part of your deployment configuration. Doing so could lead to unintended product behavior, and ultimately a request from Red Hat to redeploy the environment without the parameters configured. Adjusting these parameters is not supported in any deployment model.

Below are the list of parameters that should not be edited as part of your deployment configuration:

  • aapName
  • crossTenantRoleAssignment
  • engineAutoRetrySteps
  • engineContainerImage
  • engineEndWait
  • engineSaveContainer
  • engineTemplateUrl
  • includedNodes
  • operatorsChannel
  • operatorsIndex
  • planId
  • starttime
Product(s)
Category
Tags
Article Type