[Feature]: Cleanup .Azure\ErrorRecords

[dcaro]

Description of the new feature

The ~/.Azure/ErrorRecords folder has a log of all failed cmdlets.
We should clean this folder on a regular basis or not use it depending how the content is used.

Proposed implementation details (optional)

No response

[alunmj]

The context I encountered it in is an Azure Function in PowerShell, whose home directory is limited to 64MB (seems not to be configureable), and was running into random-seeming issues ("The term Connect-AzAccount is not recognized", auth errors related to certificates not being loaded, identity issues, unable to load modules...), which were only solved when we finally lucked on an error message telling us that there was no space left on the device. Finding which device proved challenging.
On my laptop, I have 256MB of ErrorRecords going back to 2019. The Azure Function now contains a daily 'reaper' which goes through and clears this folder out, but it would be nice not to have to.

[isra-fel]

Thank you @alunmj for providing the context 😀
We need to reconsider the benefit of having the error records and decide the action to take.

• Regularly clean up the folder
• A global switch
• Remove the feature

[alunmj]

Two other options come to mind, although you might immediately discard them:

• Document that it exists in the first place
• Check for available space before writing the records
• Throw an exception when the last ErrorRecord write fills the disk, so the error describes the problem, rather than causing later problems with no information

[dcaro]

@Francisco-Gamino FYI

[Francisco-Gamino]

Hello @dcaro -- Is Azure PowerShell the only one writing content to this location? Also, we noticed that at ~/.Azure there are other folders, .e.g., commands, ErrorRecords, logs, and telemetry. Should these also be deleted on regular basis?

/cc @AnatoliB @michaelpeng36 @shreyabatra4

[isra-fel]

cc @jiasli does CLI owns any of the directories in .Azure?

[tylermcvaney]

@alunmj, I also am encountering a similar error with ("The term Connect-AzAccount is not recognized") in my Azure Function App. After extensive troubleshooting, we discovered that the issue was related to insufficient disk space. The error message also pointed to a lack of space in the '~/.Azure' directory. Considering Azure Function Apps are a PaaS, this is very difficult for users to diagnose.