Frank Rehwinkel (May 13 2024 at 13:45): Frank Rehwinkel (May 13 2024 at 13:45):Is it the expected default that building wac and trying to use it to replace wasm-tools compose means access to my keychain has to be granted, I guess to access wa.dev if it runs into the need?
I'm trying to run wac plug to see how it can replace the wasm-tools compose in a build script and the mac OS is asking me if it should grant the program permission to use my confidential information for the warg-auth-token. The Wasm components I'm trying to compose with are all local.
I could try reinstalling wac without the registery feature for now, but I still wonder what the plan for accessing confidential information is, for uses that shouldn't require it.
Lann Martin (May 13 2024 at 13:49):I would say that is probably a bug; could you open an issue please?
Frank Rehwinkel (May 13 2024 at 14:05):Okay, will open an issue. Will add that even when I disallowed access, the composition proceeded and the results were correct. In the build script, I could replace wasm-tools compose with wac plug and the multiple argument flags of -d with --plug and otherwise the new command was just a slip in for the old one and wasmtime could run the resulting component as before. Nice.
Notification Bot (May 13 2024 at 14:16):Frank Rehwinkel has marked this topic as resolved.
Last updated: Dec 06 2025 at 05:03 UTC