Feature work/notes/fixes for PoC

[alecthomas]

Must build:

• Flutter work (@wesbillman)(didpay)
• General purpose HTTP ingress support #741 (@wesbillman)
• API for secrets (@worstell and @alecthomas)
• API for database connection access (@worstell and @alecthomas)
• We need a way to run tests #785
• Codegen TypeScript templates (@wesbillman) (https://github.com/tbdeng/pfi/pull/30)
• Improve the HTTP FTL ingress API experience #805 (epic)
• Make ftl dev smarter about when to rebuild and redeploy. #792
• Decrease logging noise during development #869

Future work/notes:

[mistermoe]

@alecthomas would a queueing mechanism be too chonky to add to this issue or does it make sense to track separately?

[alecthomas]

Ah, no, I knew there was something I was forgetting. I'll add it.

[alecthomas]

What queueing pattern(s) do you need initially? The patterns are described here

[mistermoe]

i think pubsub would likely be best!

[alecthomas]

Hehe well there are two patterns: fanout and first-come first-served. I assume you mean first-come first-served? Where multiple consumers consume from a single subscription to a topic.

[mistermoe]

ah aye apologies. i scrolled to the top of the doc and read "messaging patterns" so thought you were asking which of the messaging patterns first. should've just looked at exactly where you linked! correct pubsub first-come first-served

[alecthomas]

@mistermoe can you send us the link to your KMS interface code please?

[alecthomas]

https://github.com/TBD54566975/web5-kt/blob/main/crypto/src/main/kotlin/web5/sdk/crypto/KeyGenerator.kt

[alecthomas]

Moved all the other issues to the #728