Upsert Functionality for Integration Entity by Identifier
Hi there, I'd like to add this functinality, this should be easy and quick.
The goal of this proposal is to introduce an upsert endpoint for the integration entity within Novu's API. The upsert operation combines the functionality of both "update" and "insert" operations, allowing clients to either update an existing integration or create a new one if it does not already exist.
2 Replies
Hey @abdlrahmansaber. 🙂 can you share the underline use case of this? Do you have an idea on how to diffrentiate the update from the create?
Hey @Tomer Barnea, sorry for the late reply and thanks for the quick response 🙂. Our primary use case involves deploying our service on Kubernetes. We have environment variables that may change, and with multiple organizations, the namespace determines the service deployment. Our current process involves first checking if the providers are created; if not, we create them. After that, we check if the environment variables have changed. If they have, we update them.
Using
upsert could streamline this process by allowing us to use a unique identifier to either update or create the providers without needing to separately check their existence.