-
Notifications
You must be signed in to change notification settings - Fork 13
Updating the ophan acquisitions model
Tom Forbes edited this page May 14, 2020
·
1 revision
Our backends send acquisition events to Data Lake via Ophan. This isn't ideal because it means we're tied to Ophan's model. We should eventually migrate to sending events direct to Data Lake and maintain our own model. For now, the process for updating the acquisition model is as follows:
- Create a branch on ophan. Update the thrift model here here. Then follow the guide here to update the avro schema. Create a PR.
- After merging the ophan change, release the event-model library with
release cross
from theeventModel
project in sbt. - Create a branch on ophan-data-lake. As described in the guide, copy the latest .avsc file from
ophan/avro-logger/src/test/resources/schemas/
toophan-data-lake/ophan_event.avsc
and create a PR. - Create a branch on acquisition-event-producer. Update the
ophan-event-model
dependency in the build.sbt, and after merging runsbt release
. - Create a branch on support-frontend. Update the
acquisition-event-producer-play26_2.12
dependency in support-models/build.sbt. - After merging the support-frontend change, release support-models. Unfortunately we need to use this branch to do this. (Once we have moved payment-api into the support-frontend mono repo we will no longer have to release support-models.)
- Create a branch on payment-api. Update the support-models dependency.
- Create a branch on acquisitions-firehose-transformer and update the
ophan-event-model
dependency
- Redux Glossary
- Why Redux Toolkit?
- Writing state slices with Redux Toolkit
- Handling action side effects in Redux
- Presentational and Container Components
- Scoped actions and reducers
- Server Side Rendering
- Form validation
- CI build process
- Post deployment testing
- Post deployment test runbook
- TIP Real User Testing
- Code testing and validation
- Visual testing
- Testing Apple Pay locally
- Test Users
- Deploying to CODE
- Automated IT tests
- Deploying Fastly VCL Snippets
- Archived Components
- Authentication
- Switchboard
- How to make a fake contribution
- The epic and banner
- Environments
- Tech stack
- Supported browsers
- Contributions Internationalisation
- Payment method internationalisation in Guardian Weekly
- Print fulfilment/delivery
- Updating the acquisitions model
- Runscope testing
- Scala Steward for dependency management
- Alarm Investigations
- Ticker data
- Ophan
- Quantum Metric
- [Google Tag Manager] (https://github.com/guardian/support-frontend/wiki/Google-Tag-Manager)