Details of the scenario you tried and the problem that is occurring
As part of the AzDevOpsProject resource, integration tests, AzureDevOps is triggering emails stating...
The team project TestProjectName has been renamed to TestProjectName in the organization
... when the name has, infact, not been updated/amended.
Suspecting it's triggered by the AzDevOpsProject_EnsureProjectUpdated_Config, integration test/config (see links below).
Suggested solution to the issue
I suspect AzureDevOps is registering the update to the Project resource via the API as a change (even though the name has not changed) so it might be worth investigating if this email (and related false-positive, change to ProjectName) can be avoided by ommitting the ProjectName from the update/PUT/PATCH request.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The specific intergration test, configurations are:
AzDevOpsProject_EnsureProjectPresent_Config (which creates the "TestProjectName" project)
AzDevOpsProject_EnsureProjectIdentical_Config (which ensures the "TestProjectName" project is left the same as it was created when reapplied - Note: Would expect DSC not to process a change in this scenario).
AzDevOpsProject_EnsureProjectUpdated_Config (which updates the project resource as a result of other property changes (ProjectDescription) athough the project name has not changed).
Suspecting the change is triggered by the AzDevOpsProject_EnsureProjectUpdated_Config, integration test - This would be triggering a call to the AzureDevOps API to make a change to an existing project.
All of the integration test configurations are located here and the respective, integration tests are here
Details of the scenario you tried and the problem that is occurring
As part of the
AzDevOpsProjectresource, integration tests, AzureDevOps is triggering emails stating...The team project TestProjectName has been renamed to TestProjectName in the organization... when the name has, infact, not been updated/amended.
Suspecting it's triggered by the
AzDevOpsProject_EnsureProjectUpdated_Config, integration test/config (see links below).Suggested solution to the issue
I suspect AzureDevOps is registering the update to the
Projectresource via the API as a change (even though the name has not changed) so it might be worth investigating if this email (and related false-positive, change toProjectName) can be avoided by ommitting theProjectNamefrom the update/PUT/PATCH request.The DSC configuration that is used to reproduce the issue (as detailed as possible)
The specific intergration test, configurations are:
AzDevOpsProject_EnsureProjectPresent_Config(which creates the "TestProjectName" project)AzDevOpsProject_EnsureProjectIdentical_Config(which ensures the "TestProjectName" project is left the same as it was created when reapplied - Note: Would expect DSC not to process a change in this scenario).AzDevOpsProject_EnsureProjectUpdated_Config(which updates the project resource as a result of other property changes (ProjectDescription) athough the project name has not changed).Suspecting the change is triggered by the
AzDevOpsProject_EnsureProjectUpdated_Config, integration test - This would be triggering a call to the AzureDevOps API to make a change to an existing project.All of the integration test configurations are located here and the respective, integration tests are here