azure-docs
azure-docs copied to clipboard
MicrosoftDocs
How to manage dev and production endpoints
Hello,
I'd like to ask for guidance on how to manage dev and production inputs/outputs. During local development I use publicly available event hub namespace, nevertheless for production I need to allow only trusted Azure services to connect to Event Hub thus I need to create input/output definitions with Managed Identity. Please can you provide guidance on how I can keep test input/output definitions in the git/code base but when running deployment pipeline have only production input/outputs captured in the generated ARM template?
Thank you.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 69104dfd-0c8f-16eb-f42b-8543d3b90855
- Version Independent ID: c8e6dd18-dfb5-42dc-33e1-85d2becf9923
- Content: Automate builds, tests, and deployments of an Azure Stream Analytics job using CI/CD tools
- Content Source: articles/stream-analytics/cicd-tools.md
- Service: stream-analytics
- GitHub Login: @su-jie
- Microsoft Alias: sujie
@MarekLani Thanks for your feedback! We will investigate and update as appropriate.
@MarekLani
We understood that the MSI is not supported for our local run yet. But if this capability is ready, you could use the same configuration of the input/output with MSI for your local run development and online deployment. This feature is planned, and in progress.
As of now, a workaround is to keep your source code in GIT with MSI configuration, before starting the localrun, please update the input/output configuration files with your connection string temporary in local.
Sorry for the inconvenience.
@pengyuli-ms @alexlzx @ruiminwang
Thank you for feedback and guidance, this is actually approach I took, it just requires some caution when pushing changes to git. Please any expectations on availability of msi for local dev? Thank you.
This will be available in early of next year.
btw: this is the azure doc github. We have our ASA VSCode extension github which is used to capture the customers' issues for our local debug tooling: ASA VScode extension: https://github.com/microsoft/vscode-asa/issues. I've moved this issue to there.
Let's get this item closed and follow up this issue in that github: https://github.com/microsoft/vscode-asa/issues/81