Hello @dotnet_guy
Let’s break down the problem and explore potential solutions:
- Artifact Already Exists Error: The error message “Event Hub already exists” suggests that the service connection might already be present, and you may not have the appropriate permissions to view or modify it. To address this, follow these steps:
- Go to Project settings in Azure DevOps.
- Navigate to Service connections under Pipelines.
- Check if the “Windows Azure MSDN - Visual Studio Premium” service connection already exists.
- Custom Partition Count Issue: If the Event Hub is not taking your custom partition count and defaults to 4, consider the following:
- Ensure that your Terraform configuration specifies the desired partition count correctly.
- Verify that there are no conflicting settings or overrides in your pipeline or Terraform files.
- Check for any recent changes in your Terraform modules or Azure DevOps pipeline configurations.
- Incoming Event Sources: Removing all incoming event sources to the Event Hub allows you to delete and deploy it successfully. However, this approach is not ideal due to the hassle of coordinating CRs from multiple teams.
- Consider reviewing the incoming event sources and their impact on the Event Hub. Is there a way to manage these sources more efficiently?
- Explore whether you can dynamically adjust the configuration based on the presence of incoming sources.
- Recent Changes: It’s essential to check for any recent updates or changes in Azure DevOps, Terraform, or Event Hub behavior. Review release notes, documentation, and community forums to identify any relevant updates or known issues.
Remember to involve your team members and Azure DevOps experts to troubleshoot further.
I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.