Skip to content

Conversation

@Abban
Copy link
Member

@Abban Abban commented Jul 29, 2025

Sometimes we need to run the anonymiser in order to
investigate issues in our application. This adds a
command to allow it from the developer environment.

Ticket: https://phabricator.wikimedia.org/T400323

@Abban Abban requested a review from a team as a code owner July 29, 2025 12:52
@Abban Abban requested review from Sperling-0, gbirke and moiikana July 29, 2025 12:52
Sometimes we need to run the anonymiser in order to
investigate issues in our application. This adds a
command to allow it from the developer environment.

Ticket: https://phabricator.wikimedia.org/T400323
@Abban Abban force-pushed the anonymise-all-donations-command branch from 66d64c4 to c71b8c2 Compare July 30, 2025 10:37
Copy link
Member

@gbirke gbirke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We deploy the cli directory together with the rest of the application, which means that theoretically we could accidentally run this in production.

I'm not sure about the use case scenario for this. If you need anonymised donations to test something on a confirmation page, we should rather have a command that inserts test data (reusing fixtures from teh donation bounded context). If you want to test anonymization code, you could insert the fixtures in the FOC (it already has a command to insert them) and run the regular anonymization command there.

If we can come up with a good scenario why we need this, we should add an APP_ENV check to the command and only allow this for dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants