Manage Azure Event Hub assets

In general, these should be:

• Created in top-down order (connection, then AzureEventHub, then AzureEventHubConsumerGroup)
• Deleted in bottom-up order (consumer groups, then event hubs, then connections)¹

Asset structure

Connection

An Azure Event Hub connection requires a name and qualifiedName. For creation, specific settings are also required to distinguish it as an Azure Event Hub connection rather than another type of connection. In addition, at least one of adminRoles, adminGroups, or adminUsers must be provided.

Java

Create an Azure Event Hub connection

String adminRoleGuid = client.getRoleCache().getIdForName("$admin"); // (1)
Connection connection = Connection.creator( // (2)
        "event-hub-connection", // (3)
        AtlanConnectorType.AZURE_EVENT_HUB, // (4)
        List.of(adminRoleGuid), // (5)
        List.of("group2"), // (6)
        List.of("jsmith")) // (7)
    .build();
AssetMutationResponse response = connection.save(client); // (8)
String connectionQualifiedName = response.getCreatedAssets().get(0).getQualifiedName(); // (9)

1. Retrieve the GUID for the admin role, to use later for defining the roles that can administer the connection.
2. Build up the minimum request to create a connection.
3. Provide a human-readable name for your connection, such as production or development.
4. Set the type of connection to AZURE_EVENT_HUB.
5. List the workspace roles that should be able to administer the connection (or null if none). All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUIDs of the workspace roles. At least one of adminRoles, adminGroups, or adminUsers must be provided.
6. List the group names that can administer this connection (or null if none). All users within that group (current and future) will be administrators of the connection. Note that the values here are the names of the groups. At least one of adminRoles, adminGroups, or adminUsers must be provided.
7. List the user names that can administer this connection (or null if none). Note that the values here are the usernames of the users. At least one of adminRoles, adminGroups, or adminUsers must be provided.
8. Actually call Atlan to create the connection. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
9. Retrieve the qualifiedName for use in subsequent creation calls. (You'd probably want to do some null checking first.)

Python

Create an Azure Event Hub connection

from pyatlan.client.atlan import AtlanClient
from pyatlan.model.assets import Connection, AzureEventHub, AzureEventHubConsumerGroup
from pyatlan.model.enums import AtlanConnectorType

client = AtlanClient()
admin_role_guid = client.role_cache.get_id_for_name("$admin") # (1)
connection = Connection.creator( # (2)
    client=client,  # (3)
    name = "event-hub-connection", # (4)
    connector_type = AtlanConnectorType.AZURE_EVENT_HUB, # (5)
    admin_roles = [admin_role_guid], # (6)
    admin_groups = ["group2"], # (7)
    admin_users = ["jsmith"] # (8)
)

response = client.asset.save(connection) # (9)
connection_qualified_name = response.assets_created(asset_type=Connection)[0].qualified_name # (10)

1. Retrieve the GUID for the admin role, to use later for defining the roles that can administer the connection.
2. Build up the minimum request to create a connection.
3. You must provide a client instance.
4. Provide a human-readable name for your connection, such as production or development.
5. Set the type of connection to AZURE_EVENT_HUB.
6. List the workspace roles that should be able to administer the connection (or None if none). All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUIDs of the workspace roles. At least one of admin_roles, admin_groups, or admin_users must be provided.
7. List the group names that can administer this connection (or None if none). All users within that group (current and future) will be administrators of the connection. Note that the values here are the names of the groups. At least one of admin_roles, admin_groups, or admin_users must be provided.
8. List the user names that can administer this connection (or None if none). Note that the values here are the usernames of the users. At least one of admin_roles, admin_groups, or admin_users must be provided.
9. Actually call Atlan to create the connection.
10. Retrieve the qualifiedName for use in subsequent creation calls. (You'd probably want to do some None checking first.)

Kotlin

Create an Azure Event Hub connection

val adminRoleGuid = client.roleCache.getIdForName("\$admin") // (1)
val connection = Connection.creator( // (2)
        "event-hub-connection", // (3)
        AtlanConnectorType.AZURE_EVENT_HUB, // (4)
        listOf(adminRoleGuid), // (5)
        listOf("group2"), // (6)
        listOf("jsmith")) // (7)
    .build()
val response = connection.save(client) // (8)
val connectionQualifiedName = response.createdAssets[0].qualifiedName // (9)

1. Retrieve the GUID for the admin role, to use later for defining the roles that can administer the connection.
2. Build up the minimum request to create a connection.
3. Provide a human-readable name for your connection, such as production or development.
4. Set the type of connection to AZURE_EVENT_HUB.
5. List the workspace roles that should be able to administer the connection (or null if none). All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUIDs of the workspace roles. At least one of adminRoles, adminGroups, or adminUsers must be provided.
6. List the group names that can administer this connection (or null if none). All users within that group (current and future) will be administrators of the connection. Note that the values here are the names of the groups. At least one of adminRoles, adminGroups, or adminUsers must be provided.
7. List the user names that can administer this connection (or null if none). Note that the values here are the usernames of the users. At least one of adminRoles, adminGroups, or adminUsers must be provided.
8. Actually call Atlan to create the connection. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
9. Retrieve the qualifiedName for use in subsequent creation calls. (You'd probably want to do some null checking first.)

Raw REST API

POST /api/meta/entity/bulk

{
  "entities": [
    {
      "typeName": "Connection", // (1)
      "attributes": {
        "name": "event-hub-connection", // (2)
        "connectorName": "azure-event-hub", // (3)
        "qualifiedName": "default/azure-event-hub/123456789", // (4)
        "category": "eventbus", // (5)
        "adminRoles": [ // (6)
          "e7ae0295-c60a-469a-bd2c-fb903943aa02"
        ],
        "adminGroups": [ // (7)
          "group2"
        ],
        "adminUsers": [ // (8)
          "jsmith"
        ]
      }
    }
  ]
}

1. The typeName must be exactly Connection.
2. Human-readable name for your connection, such as production or development.
3. The connectorName must be exactly azure-event-hub.
4. The qualifiedName should follow the pattern: default/azure-event-hub/<epoch>, where <epoch> is the time in milliseconds at which the connection is being created.
5. The category must be eventbus.
6. List any workspace roles that can administer this connection. All users with that workspace role (current and future) will be administrators of the connection. Note that the values here need to be the GUIDs of the workspace roles. At least one of adminRoles, adminGroups, or adminUsers must be provided.
7. List any groups that can administer this connection. All users within that group (current and future) will be administrators of the connection. Note that the values here are the names of the groups. At least one of adminRoles, adminGroups, or adminUsers must be provided.
8. List any users that can administer this connection. Note that the values here are the usernames of the users. At least one of adminRoles, adminGroups, or adminUsers must be provided.

Access policies

Atlan creates the policies that grant access to a connection, including the ability to retrieve the connection and to create assets within it, asynchronously. It can take several seconds (even up to approximately 30 seconds) before these are in place after creating the connection.

You may therefore need to wait before you'll be able to create the assets below within the connection.

To confirm access, retrieve the connection after it has been created. The SDKs' retry loops will automatically retry until the connection can be successfully retrieved. At that point, your API token has permission to create the other assets.

Note: if you are reusing an existing connection rather than creating one via your API token, you must give your API token a persona that has access to that connection. Otherwise all attempts to create, read, update, or delete assets within that connection will fail due to a lack of permissions.

AzureEventHub

An AzureEventHub requires a name and a qualifiedName. For creation, you also need to specify the connectionQualifiedName of the connection for the event hub.

Java

Create an Azure Event Hub

AzureEventHub eventHub = AzureEventHub.creator( // (1)
        "myAzureEventHub", // (2)
        connectionQualifiedName) // (3)
    .build();
response = eventHub.save(client); // (4)
eventHub = response.getResult(eventHub); // (5)

1. Build up the minimum request to create a event hub.
2. Provide a human-readable name for your event hub.
3. Provide the qualifiedName of the Azure Event Hub connection.
4. Actually call Atlan to create the event hub. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
5. Retrieve the created event hub for use in subsequent creation calls.

Python

Create an Azure Event Hub

event_hub = AzureEventHub.creator( # (1)
    name="myAzureEventHub", # (2)
    connection_qualified_name=connection_qualified_name # (3)
)
response = client.asset.save(event_hub) # (4)
event_hub_qualifed_name = response.assets_created(asset_type=AzureEventHub)[0].qualified_name # (5)

1. Build up the minimum request to create a event hub.
2. Provide a human-readable name for your event hub.
3. Provide the qualifiedName of the Azure Event Hub connection.
4. Actually call Atlan to create the event hub.
5. Retrieve the created event hub for use in subsequent creation calls. (You'd probably want to do some None checking first.)

Kotlin

Create an Azure Event Hub

var eventHub = AzureEventHub.creator( // (1)
        "myAzureEventHub", // (2)
        connectionQualifiedName) // (3)
    .build()
response = eventHub.save(client) // (4)
eventHub = response.getResult(eventHub) // (5)

1. Build up the minimum request to create a event hub.
2. Provide a human-readable name for your event hub.
3. Provide the qualifiedName of the Azure Event Hub connection.
4. Actually call Atlan to create the event hub. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.
5. Retrieve the created event hub for use in subsequent creation calls.

Raw REST API

POST /api/meta/entity/bulk

{
  "entities": [
    {
      "typeName": "AzureEventHub", // (1)
      "attributes": {
        "name": "myAzureEventHub", // (2)
        "qualifiedName": "default/azure-event-hub/123456789/topic/myAzureEventHub", // (3)
        "connectionQualifiedName": "default/azure-event-hub/123456789", // (4)
        "connectorName": "azure-event-hub" // (5)
      }
    }
  ]
}

1. The typeName must be exactly AzureEventHub.
2. Human-readable name for your event hub.
3. The qualifiedName should follow the pattern: default/azure-event-hub/<epoch>/topic/<name>, where default/azure-event-hub/<epoch> is the qualifiedName of the connection for this event hub and <name> is the unique name for this event hub.
4. The connectionQualifiedName must be the exact qualifiedName of the connection for this event hub.
5. The connectorName must be exactly azure-event-hub.

AzureEventHubConsumerGroup

An AzureEventHubConsumerGroup requires a name and a qualifiedName. For creation, you also need to specify the list of eventHubQualifiedNames of the event hubs that will contain the consumer group.

Java

Create an Azure Event Hub consumer group

AzureEventHubConsumerGroup consumerGroup = AzureEventHubConsumerGroup.creator( // (1)
        "myEventHubConsumerGroup", // (2)
        List.of(eventHub)) // (3)
    .build();
response = consumerGroup.save(client); // (4)

1. Build up the minimum request to create a consumer group.
2. Provide a human-readable name for your consumer group.
3. Provide the list of event hubs for this consumer group.
4. Actually call Atlan to create the consumer group. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.

Python

Create an Azure Event Hub consumer group

consumer_group = AzureEventHubConsumerGroup.creator( # (1)
    name="myEventHubConsumerGroup", # (2)
    event_hub_qualified_names=[event_hub_qualified_name], # (3)
)
response = client.asset.save(consumer_group) # (4)

1. Build up the minimum request to create a consumer group.
2. Provide a human-readable name for your consumer group.
3. Provide the list of qualified_names of the event hub for this consumer group.
4. Actually call Atlan to create the consumer group.

Kotlin

Create an Azure Event Hub consumer group

val consumerGroup = AzureEventHubConsumerGroup.creator( // (1)
        "myEventHubConsumerGroup", // (2)
        listOf(eventHub)) // (3)
    .build()
response = consumerGroup.save(client) // (4)

1. Build up the minimum request to create a consumer group.
2. Provide a human-readable name for your consumer group.
3. Provide the list of event hubs for this consumer group.
4. Actually call Atlan to create the consumer group. Because this operation will persist the asset in Atlan, you must provide it an AtlanClient through which to connect to the tenant.

Raw REST API

POST /api/meta/entity/bulk

{
  "entities": [
    {
      "typeName": "AzureEventHubConsumerGroup", // (1)
      "attributes": {
        "name": "myEventHubConsumerGroup", // (2)
        "qualifiedName": "default/azure-event-hub/123456789/consumer-group/myAzureEventHub/myEventHubConsumerGroup", // (3)
        "connectionQualifiedName": "default/azure-event-hub/123456789", // (4)
        "connectorName": "azure-event-hub", // (5)
        "kafkaTopics": [{ // (6)
          "typeName": "AzureEventHub", // (7)
          "uniqueAttributes": { // (8)
            "qualifiedName": "default/azure-event-hub/123456789/topic/myAzureEventHub",
          }
        }],
        "kafkaTopicQualifiedNames": ["default/azure-event-hub/123456789/topic/myAzureEventHub"], // (9)
      }
    }
  ]
}

1. The typeName must be exactly AzureEventHubConsumerGroup.
2. Human-readable name for your consumer group.
3. The qualifiedName should follow the pattern: default/azure-event-hub/<epoch>/consumer-group/<event_hub_name>/<name>, where default/azure-event-hub/<epoch> is the qualifiedName of the connection that contains this consumer group and <name> is the unique name for this consumer group.
4. The connectionQualifiedName must be the exact qualifiedName of the connection for this consumer group.
5. The connectorName must be exactly azure-event-hub.
6. The list of event hubs in which this consumer group exists is embedded in the kafkaTopics attribute.
7. The typeName for this embedded reference must be AzureEventHub.
8. To complete the reference, you must include a uniqueAttributes with the qualifiedName of the event hub. Note: the event hub must already exist in Atlan before creating the consumer group.
9. The list of event hub qualified names.

Available relationships

Every level of the Azure Event Hub structure is an Asset, and can therefore be related to the following other assets.

Footnotes

1. Although if you want to delete everything in a connection, your better avenue is the packaged connection delete utility in the UI. ↩