The following illustrates an unencrypted JSON configuration file that can be produced when exporting Azure visibility jobs. If needed, you can modify this configuration file to address differences between systems.
Note:
- You can use this or another exported configuration file as a template for a new configuration file that can be imported to a different system.
- The keys within
options
keys are required. If necessary, you can modify the values in theoptions
section with valid content for the new system.
Attention: If you are running any visibility jobs in another Cloud Discovery
& Visibility (CDV) instance, BlueCat recommends stopping any running visibility jobs
on the old instance before importing and running the visibility jobs in the new
CDV instance.
{
"Microsoft Azure":[
{
"bam_url":"https://1.1.1.1",
"bam_username":"test",
"hash_id":"test",
"id":1,
"options":{
"authentication":{
"azure_client_id":"test",
"azure_client_secret":"test",
"azure_resource_group":"test",
"azure_subscription_id":"test",
"azure_tenant_id":"test",
"is_new_format_configuration":true,
"is_running_on_native_cloud":false
},
"auto_create_subzone":false,
"bluecat_configuration":"AzureConfig",
"configuration_mode":"custom",
"device_external_view":"",
"device_internal_view":"",
"dns_private_view":"",
"dns_public_view":"",
"dynamic_update":false,
"external_name_resolution":false,
"internal_name_resolution":false,
"k8s_service":false,
"load_balancers":false,
"override_configuration":true,
"private_dns_zones":false,
"private_endpoint_view":"",
"private_endpoints":false,
"private_networks":true,
"public_dns_zones":false,
"public_networks":true,
"remove_deleted_resources":false,
"target_domain":"",
"virtual_machines":false,
"visibility":{
"bam_password":"test",
"bam_username":"test",
"eg_subscription_name":"",
"reuse_queue_name":false,
"sb_namespace_name":"",
"sb_queue_name":"",
"selective_deployment":false
}
},
"platform":"Microsoft Azure",
"status":"running"
}
]
}