Please export extensionAPIClient
- Lingua principale
- Go
- Stelle
- 3.8k
- Fork
- 578
- Merge medio
- 8h 18m
- PR unite (30g)
- 1
Descrizione
**Is your feature request related to a problem? Please describe.**
Occasionally would like to write a small Lambda extension to do some processing after my main Lambda handler has returned a response. While the requirements for implementing an extension are well-documented, there's no official 1st-party public Go package to help with implementation.
**Describe the solution you'd like**
`package lambda` already has implemented an extension client, but it is unexported. I'd like to be able to create a new extension client by calling some constructor `NewExtensionAPIClient` (which could be in `package lambda` or in some other package), register event types I'm interested in, and define an extension event handler.
It seems to me that this would not add much maintenance burden since the extension client is already implemented for the sake of the `WithEnableSIGTERM` option. The difference here would be supporting the exported API for the extension client.
**Describe alternatives you've considered**
I could implement and maintain an extension API client myself; but the same is true for implementing a runtime API client. I'd rather rely on an officially supported implementation.
I could find a 3rd-party implementation, but since there's no single or few 3rd-party implementations that have gained community consensus, I don't have any assurances about the quality of the implementation.
---
I'd like to express my thanks to those maintaining this repository. I use it a lot, and I appreciate your work.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia nel package lambda individuando il client per le estensioni non esportato esistente utilizzato da WithEnableSIGTERM, quindi confronta le operazioni supportate con la documentazione di Lambda Extensions API. Il lavoro è completo quando gli autori di estensioni possono utilizzare un client Go pubblico ufficiale con il flusso di costruttore, registrazione degli eventi e handler descritto nell’issue.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- go
- Ambito
- api, cloud
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100