Skip to content

Conversation

@sachin-sumologic
Copy link
Collaborator

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 48 out of 51 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

# ============================================================================
azure_subscription_id = "your-azure-subscription-id" # Your Azure subscription ID
azure_client_id = "your-azure-client-id" # Service principal client ID
azure_client_secret = "your-azure-client-secret" # Service principal secret
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can these be found by the user, the subscription ID and Tenant ID are easy to find but client ID and client secret we need to create service principal in that the client secret is created. Should we mention that or a link of how to do so?

In the above section in Config variables we only have explained what it is and not how can we create it


## Troubleshooting

### Azure Event Hub Regional Support
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think mentioning the number of eventhubs instances different tiers i.e basic, standard etc can handle should be added in this section. The user may face errors if using standard and more than 10 instances are being created and will visit this section to troubleshoot.

terraform destroy
```

**⚠️ Warning**: This will:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we move This will to next line ?? Same line has two colons :


### Azure Event Hub Regional Support

The table below shows Event Hub namespace availability across Azure regions by SKU tier. This module automatically handles region-specific SKU limitations.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The table below shows Event Hub namespace availability across Azure regions by SKU tier. This module automatically handles region-specific SKU limitations.
The tables below show Event Hub namespace availability across Azure regions by SKU tier. This module automatically handles region-specific SKU limitations.


- **Scope**. Activity logs capture ALL operations across the ENTIRE subscription (all resource groups, all resources).
- **Single Configuration**. Azure only allows **ONE** diagnostic setting for activity logs per subscription.
- **Shared Resource**. If multiple Terraform configurations or users enable activity logs on the same subscription, **only the last one applied will be active**.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Shared Resource**. If multiple Terraform configurations or users enable activity logs on the same subscription, **only the last one applied will be active**.
- **Shared Resource**: If multiple Terraform configurations or users enable activity logs on the same subscription, **only the last one applied will be active**.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change for Scope, Single Configurations and Deletion Impact as well replace "." with ":"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants