You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, there are two sets of installation logs:
The logs from the Jenkins job that resides on the modm virtual machine
The Azure deployment logs that are tied to the managed resource group
If the modm virtual machine is deleted, access to the terraform installation logs will be gone.
Terraform installation logs should be copied to durable storage so that the customer have have access to them after the installer has been deleted.
Success Criteria
A blob storage account is created by default. In the future, the createUiDefinition will enable using an existing blob storage account
After a deployment completes, whether or not it is successful, the installation/diagnostics logs will be copied to a blob storage container.
Justification
Customers or publishers may want access to the diagnostics logs for later analysis or troubleshooting. This feature enables that.
Implementation
Add Azure Blob Storage with a container named Diagnostics to the mainTemplate.json
Call JenkinsDeploymentEngine's GetLogs() method and write to the blob storage account created in the previous step
The content you are editing has changed. Please copy your edits and refresh the page.
Requirement
As of now, there are two sets of installation logs:
If the modm virtual machine is deleted, access to the terraform installation logs will be gone.
Terraform installation logs should be copied to durable storage so that the customer have have access to them after the installer has been deleted.
Success Criteria
Justification
Customers or publishers may want access to the diagnostics logs for later analysis or troubleshooting. This feature enables that.
Implementation
Tasks
The text was updated successfully, but these errors were encountered: