Johan Abbors

It's not the customer that requires it explicitly, it's more of an internal compliance towards customers' requirements where a history would be useful. It can be accomplished with SQL functions,...

Yeah, in the mean time we can track history with a trigger. I plan on creating the table and trigger with a migration. I can share the final result when...

A migration (for PostgresSQL) to track history of applied migrations. ``` BEGIN; SET ROLE 'postgres'; CREATE TABLE schema_migrations_history ( id SERIAL PRIMARY KEY NOT NULL, version BIGINT NOT NULL, applied_at...

We have several production environments and it's common that some environments fall behind both in regards of deploying application upgrades and new migrations. For this reason, auditability is preferred in...

@amanangira this is the implementation that we are using https://github.com/golang-migrate/migrate/issues/179#issuecomment-479740765. It meets our requirements and have been working so far. Below is a sample from the table in a live...

A good practice that we have adapted is to create the trigger as the very first migration for new databases, ie. `0000_initial.up.sql`

A question if the manifest tooling support the following use case? Background: One of our core applications is a Django web app which manages the database schema with its own...

@dhui Thanks for clarifying. > interoperability with other migration tools/systems/frameworks is not a goal for migrate. You're right, I'm not asking for it and I won't. We happen to use...

I'd also like to see an improvement here. It would be great if the secrets could be integrated with vault since we rely on vault for 90% of our workloads....

> and sorry to spam but did you try here https://github.com/goharbor/harbor-helm/blob/master/templates/core/core-cm.yaml#L43 to set harbor-registry.harbor.svc.cluster.local:5000 instead of harbor-registry:5000? In some componetns deployments, it made istio "happy" I just tried this and...