Creating the Cloud Resolver configuration file - BlueCat Cloud Resolver - 1.7.2

[
    {
        "tenant_id": <tenant_id>,
        "client_id": <client_id>,
        "client_secret_url": <value>,
        "azure_cloud": <value>
    }
    ...
]

[
    {
        "account": <account_name>,
        "role_asn": <role_asn>,
        "role_session_name": <value>
    }
    ...
]

[
    {
        "project_id": <id>,
        "auth_path":
            {
                "account_file_path": <path>
            }
    },
    {
        "project_id": <id>,
        "auth_path":
            {
                "secret_manager_path": <path>
            }
    }
]

• The project_id must be the project ID in GCP. For example, example-cr-gcp-project.
• The auth_path determines the method for authenticating against the project. The auth_path can contain the following:
  Note: You can define two authentication methods within the list.
  • The account_file_path is the absolute file path to where the service account key file is stored. For example, /Users/admin/accounts/example-cr-gcp-project-abcdef012345.json.
  • The secret_manager_path is the path to where the service account key file is stored in Secret Manager. For example, projects/1234567890/secrets/CR_SERVICE_ACCOUNT_FILE.
    Note: The path can be found in the Secret Manager Console on the Secret details page in GCP.

• For snapshots stored in an AWS S3 bucket, set the CRS_SNAPSHOT_PATH value to the name of the AWS S3 bucket. For example, cr-data.
• For snapshots stored in an Azure Blob storage, set the CRS_SNAPSHOT_PATH value to the URL of the Azure Blob storage. For example, https://test.blob.core.windows.net/snapshot.

CRS_AUTH_NS_HOST_RECORDS=
'[{"name": "tester1.bluecat.com",
"ip_addrs": ["10.200.200.99","10.200.200.98"]},
{"name": "tester2.bluecat.com",
"ip_addrs": ["10.200.200.95", 
"fe80::feeb:7f3a:eaad:3e3c"]}]'