The following illustrates an unencrypted JSON configuration file that can be produced when exporting Azure scheduled discovery 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
optionskeys are required. If necessary, you can modify the values in theoptionssection with valid content for the new system.
Attention: If you wan to run visibility jobs in another CDV instance, BlueCat
recommends stopping any running scheduled discovery jobs in the old CDV instance before
importing and running the scheduled discovery jobs in the new CDV instance.
{
"Microsoft Azure":[
{
"bam_url":"https://1.1.1.1",
"bam_username":"test",
"hash_id":"1a8163eef05d2d46345cb291151cbf18",
"id":1,
"interval":60,
"options":{
"authentication":{
"azure_client_id":"abcd1234-6739-0123-aaa1-09a87b65c432",
"azure_client_secret":"gAAAAABk",
"azure_resource_group":"test_group",
"azure_subscription_id":"abcd1234-1dc8-463d-8d6d-09a87b65c432",
"azure_tenant_id":"abcd1234-d415-4d83-94b7-09a87b65c432",
"is_running_on_native_cloud":false
},
"options":{
"auto_create_subzone":false,
"bluecat_configuration":"Azure",
"create_separate_configuration":true,
"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":false,
"remove_deleted_resources":true,
"target_domain":"",
"virtual_machines":true
},
"schedule":{
"bam_password":"gAAAAA",
"bam_username":"test",
"interval":600
},
"visibility":null
},
"platform":"Microsoft Azure",
"previous_execute_time":"03/17/2023 10:31:17",
"status":"completed"
}
]
}