Esteban Rey

I've been trying to run oav extract-xmsexamples to get examples for our swagger spec . To this point I am using session recordings I generated using the Azure .Net Sdk...

[Userspace Convertor] Overlaybd Layer Versioning for Deduplication

2

### What is the version of your Accelerated Container Image v1.0.2 ### What would you like to be added? Layer deduplication needs to account for the underlying overlaybd-tool versions to...

This is an issue open for the purpose of tracking unit test additions to the project.

Add Custom / Descriptive HTTP User-Agent for Overlaybd

2

### What is the version of your Overlaybd v1.0.10 ### What would you like to be added? We have noticed that overlaybd seems to make requests using userAgent EASE/0.21.6. This...

Introduce a simple versioning system for the userspace convertor deduplication dbs. This prevents inconsistencies with an existing DB if a new version is used. **What this PR does / why...

## Feature Request ### Description When writing unit tests for code that interacts with the aztables client in the Azure SDK for Go, developers can typically mock most client functions...

Clarify queueLengthStrategy description in docs for Azure Queue Autoscaling

2

I noticed while reviewing the code for this path (https://github.com/kedacore/keda/blob/e89626a16563735b8cc6211fbcbdc43e51d37d15/pkg/scalers/azure_queue_scaler.go), that I had originally misinterpreted how the visibleonly queue length strategy works. This PR tries to clarify the mistaken behavior...

Improve Error Handling in Purge Path

2

## Description The current error handling in the purge deletion path does not adequately distinguish between different types of HTTP errors. This can lead to unnecessary overall failures or missed...

## Description: The current implementation of the purge command introduces the --untagged flag, which enables cleanup of untagged manifests when a specific filter is applied. However, this behavior combines the...

## Description The current logging implementation in acr-cli relies on fmt.Printf, which lacks structure and flexibility for log management and analysis, not to mention it is locking and thus not...