Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shared access signature for Azure Eventhub #7160

Closed
MourIdri opened this issue Jun 1, 2020 · 4 comments · Fixed by #22215
Closed

Shared access signature for Azure Eventhub #7160

MourIdri opened this issue Jun 1, 2020 · 4 comments · Fixed by #22215

Comments

@MourIdri
Copy link

MourIdri commented Jun 1, 2020

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Hi there.

It is possible to implement shared access signature for azure event hub ?
like it is possible to communicate with the service Azure blob in a programmatic way.

SAS token capability is implemented for Storage here :
https://www.terraform.io/docs/providers/azurerm/d/storage_account_sas.html

while the possibility to do it for Azure Hub is documented here :
https://docs.microsoft.com/en-us/rest/api/eventhub/generate-sas-token#bash
but not yet possible on Terraform.

In any case, Eventhub is the best approach to expose events from Azure to outer world ( like SIEMs : Qradar, splunk etc... )

Thanks

@Suseelraj

This comment has been minimized.

@jrblanno

This comment has been minimized.

@mashbourne
Copy link

I think this provider gets you close. Or at least can expose what app needs to create its own short lived SAS token https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/eventhub_authorization_rule

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants