The current behaviour of our operator for the stream section allows us to create FES resources. During the creation, the postgres-operator will create FES resources, publications, and replication slots. However, during deletion (when user drop the stream section from the manifest), operator only removes the FES resources, while publications and replications are not deleted. This results in need for manual deletion by someone who has administrator roles.
Changes:
refactor syncPublication() to allow sync publication (CRUD) per database
delete replication slot based on the publication it is deleted
update createOrUpdateStream() to allow resource deletion when removed from manifest
add minimal FES CRD to enable FES resources creation for E2E test
Follow up on https://github.com/zalando/postgres-operator/pull/2563
The current behaviour of our operator for the stream section allows us to create FES resources. During the creation, the postgres-operator will create FES resources, publications, and replication slots. However, during deletion (when user drop the stream section from the manifest), operator only removes the FES resources, while publications and replications are not deleted. This results in need for manual deletion by someone who has administrator roles.
Changes:
syncPublication()
to allow sync publication (CRUD) per databasecreateOrUpdateStream()
to allow resource deletion when removed from manifest