kamilmrzyglod
Joined 7 months ago
Karma
10
Submissions
22
Member since
Apr 8
Recent submissions
Comment · 4 months ago
Would love to hear your thoughts on the post and see if you had similar challenges :)
Comment · 4 months ago
Updated the title - the original was too generic for what the post actually covers. It's about Topaz, an OSS local Azure emulator I'm building.
Comment · 4 months ago
Fair point - I built Topaz, so yes, there's a conflict of interest. The argument about mock-vs-inject stands independently though: any proxy that sits between the SDK and a real endpoint would do the same thing. Topaz happens to be what I built to solve this for Azure locally.
Comment · 4 months ago
Hey, my name's Kamil and I'm the author. I started working on Topaz, local Azure emulator, over a year ago as a prototype. After validating it in a few commercial projects I was working on, I kept developing it. It's built on a principle of going deep-first - emulating not only typical CRUD operations but also intricacies of data planes (like ACR OCI protocol emulation, soft-deleting, simulating network errors, Entra ID authentication flows and similar low-level issues).
The main idea behind starting the project was providing a single tool for Azure developers with a unified DevEx - DNS, SSL, IaC support.
Would love to hear more about what gaps you see when trying to emulate Azure services and what scenarios you'd like to cover with such a tool.
Here's the before/after writeup if you want the full context - https://topaz.thecloudtheory.com/blog/replacing-azure-emulat...
Comment · 6 months ago
Yes it is but it's still another emulator which needs to be run separately, configured separately and managed separately. But let's keep that for another comparison :)