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
[MQ Goals] ARM Template for java Feature/live test resource mgmt #6801
Conversation
/azp run java - appconfiguration - tests |
Pull request contains merge conflicts. |
/azp run java - appconfiguration - tests |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run java - keyvault- tests |
No pipelines are associated with this pull request. |
/azp run java - keyvault - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
@alzimmermsft I have added needed Roles for storage account for test. Have a look at the pipeline run https://dev.azure.com/azure-sdk/internal/_build/results?buildId=228040&view=logs&j=d4b67cd2-6572-561e-035e-54acb01c3f6e&t=e0165002-68ce-55b0-d006-544d028d5587 If no more resource creation is needed for storage test, Can we consider storage ARM template complete ? |
/azp run java - eventhubs - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Those tests look to be running correctly, the failing tests have been seen outside the scope of this change. |
/azp run java - eventhubs - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - eventhubs - data |
Azure Pipelines successfully started running 1 pipeline(s). |
Closing this PR as this work was distributed in other PR specific to each library. And they are complete. |
Our goal is to create common Azure resources using ARM template for each module. And pipeline to manage common resources and drop them in end. This will save cost and remove unwanted resources after test is complete or stopped in between
There will be one ARM template per service. For example Storage will have one common arm template for Queue, File and Blob.
The pipeline will run ARM template and create common resources for example resource group, Accounts etc.
The pipeline will pass on names of these resources as ENV variable into test. For example
AZURE_APPCONFIG_CONNECTION_STRING
In the end pipeline will also delete these common resources which it created earlier and that will cause all the resources created to be removed.