alex0ptr

Yes fnox looks great. It seems the cache is directory based here and not session based. Not sure if I like that. If my agent starts to snoop around he might use other caches transparently.

A brother from another mother. I was afraid no one has similar workflows. :)

Wow this is incredibly similar. I guess it seems that the notable difference is that the cached results are written to a directory - which is exactly what I wanted to avoid. So depends on what you want to cache I guess.

If I already approved it once I already have to assume it could have been leaked. The cache doesn't change much about it if the agent / tenant is asking for something it already has.

That looks pretty cool - even supports caching. Will take a deeper look. Thx

Yes - but I'm out of ideas. How else support long running agents without leaving secrets in files or by default exposed in the environment. That way I get notified the first time before they ask for credentials.

I don't want to store them in a file since I don't trust my agents with that data. Instead, the daemon secures the values using/under an HMAC key, making them virtually impossible to guess.

Yes, exactly. This is especially frustrating when I leave an agent running for a long time and it gets stuck on my build scripts because it's waiting for my approval.

I just want to avoid leaving my credentials and secrets on the filesystem.

EDIT: I use a lot of direnv / mise. So reloading credentials with different values is common.

I’ve been working with Azure and Azure Germanyfor the past years and have a strong history with AWS.

I cannot count how many times disks were not attaching during AKS rescheduling. We build polling where we polled Entra Id for minutes until it became “eventually” consistent - not trusting a service principal until it was fetched at least one minute consistently. The slowness of Azure Functions was unbearable. On Azure germany IoT Hubs had to be “rebooted” by support constantly - which was a shocking statement in itself. The docs always lying or leaving out critical parts. The whole Premium vs Standard stuff is like selling windows licenses. The role model and UI is absolutely inconsistent.

The stability, consistency of IAM, and speed of AWS in comparison makes me truly wonder how anyone stays with Azure. One reason might be that the Windows instances are significantly cheaper though..

I think a lot of commenters ar forgetting another fact about the M1: It also offers low power cores, neural engine, a GPU and RAM all on a single die. Therefore die sizing comparisons to most desktop class cpus make little sense and money comparisons too. (Of course the article was about something different, I’m referring to the comments)