Ensure id uniqueness on `p_ci_pipeline_variables`
Before writing to multiple partitions on p_ci_pipeline_variables
we must ensure at the database level that users/developers can't generate duplicate ids. This was done on p_ci_builds
using a trigger to always assign the id from the database sequence, even if it was provided by the application.
We only need to create the trigger on the routing table now that we are running
PG14
-
SaaS - Similar to !125002 (merged) and !136445 (merged) -
Self-managed - Similar to !136452 (merged)
Edited by Max Orefice