Skip to content
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

[Feature]: Cleanup .Azure\ErrorRecords #955

Open
Francisco-Gamino opened this issue May 10, 2023 · 2 comments
Open

[Feature]: Cleanup .Azure\ErrorRecords #955

Francisco-Gamino opened this issue May 10, 2023 · 2 comments
Labels

Comments

@Francisco-Gamino
Copy link
Contributor

Francisco-Gamino commented May 10, 2023

This issue was originally from Azure PowerShell Azure/azure-powershell#21732

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.

Mitigation
If the customer function app does not have a dependency on the files (at this location), they can delete them with the following command. They can add this to one of their function's code:
Remove-Item ~/.Azure/ErrorRecords/* -ErrorAction SilentlyContinue

@jcbrooks92
Copy link

@Francisco-Gamino is the there a limit imposed on the size of the directory for different function SKUs?

@Francisco-Gamino Francisco-Gamino pinned this issue May 19, 2023
@Francisco-Gamino
Copy link
Contributor Author

The Azure PowerShell team provided a new config DisableErrorRecordsPersistence which will be available with Az 10.3.0 (will be available on 2023-09-05 PST)

Update-AzConfig -DisableErrorRecordsPersistence $true

Please use this to disable writing logs to your file system.

This config will be deprecated and replaced by 'EnableErrorRecordsPersistence' in next major Az release around November 2023. Writing error records to file system will be opt-in since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants