Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

🐛 [firestore-send-email] Support for multiple and dynamic SMTP connection URIs

Abierto
  • ¿Algo no está bien?
#1,990 1 comentario 4 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
gcp, typescript
Área
backend, cloud, databases

Línea de trabajo

El issue no menciona archivos, pruebas ni puntos de entrada; comienza localizando la extensión firestore-send-email y su ruta actual de configuración SMTP. Revisa cómo se gestionan actualmente la configuración de la extensión, los documentos de Firestore y Google Secret Manager, y después establece pruebas de aceptación para URI de conexión SMTP predeterminadas, seleccionadas, ausentes y recuperadas dinámicamente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

extension: firestore-send-email type: feature request

This feature request is for extension: firestore-send-email.

What feature would you like to see?

Enhancing flexibility and scalability for managing outbound emails by enabling dynamic SMTP server configuration based on Firestore documents or Google Secret Manager.

In more detail:
  • Introduce a new configurable parameter: useDynamicSmtpConnectionUris.
  • Enable dynamic SMTP connection URI configuration for outbound emails to support multiple SMTP outbound servers, catering to different customers' needs. This could involve storing each custom outbound SMTP connection URI in a Firestore collection or linking to a secret in Google Secret Manager 🔑 .
  • Implement synchronization of corresponding secrets in Google Secret Manager 🔑 via a Cloud Function or Firestore onWrite document trigger, empowering customers to manage their SMTP configurations autonomously.
  • For new documents in the email collection, the extension would examine the outboundSmtpServerId field (a new addition to email documents). If this field is specified and not set to "default", the extension would retrieve the connection URI from a Firestore document stored at a specified path designated by the new configurable parameter smtpConfigurationsCollection. If the document is linked to a secret, it will access the secret accordingly.
  • If outboundSmtpServerId is undefined, null, or set to "default", the base SMTP connection URI will be utilized.
How would you use it?

Incorporating these features would be particularly advantageous for scenarios involving diverse customers or varying SMTP configurations, such as allowing customers to use their own email servers for outbound email.

In addition, these enhancements open up possibilities for more tailored email communication strategies, e.g. enabling businesses to personalize their outgoing emails based on specific customer segments or preferences. This increased customization can significantly improve engagement and user experience, making the extension even more versatile for various use cases in application development.

As the implementation is highly valued, I'm available to provide additional context, clarification, or details for potential implementation. 🙏

Lenguaje dominante
TypeScript
Estrellas
979
Forks
434
Merge medio
20 h 44 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de firebase/extensions

Todos los issues de firebase/extensions

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.