Skip to content

feat: export storage account queue endpoint as a KeyVault secret

All Submissions:


  • [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
  • [NO] I have updated the documentation accordingly.
  • [YES] My code follows the code style of this project.

Current Behavior or Linked Issues


Only storage account name/key are exported.

Account name and key is, generally, not enough information to connect to the storage account. One needs to know account endpoints. And if the account is deployed with Azure DNS zone endpoints, the endpoints can't be inferred from the account name.

This change exports only the queue endpoint, because for the current project we only need to work with the Storage Queues.

I believe exporting the account key is not necessary because the seismic services (that will use the queue) should be able to connect on the endpoint using managed identity.

Does this introduce a breaking change?


  • [NO]

Other information


Edited by Konstantin Gukov

Merge request reports