-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TCM-417] Integrate Site Editor with Audit app #467
Conversation
…lock version" events (#466)
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few suggestions
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What problem is this solving?
This PR collects events from Site Editor and sends them to Audit App. These events are described in this epic (TCM-428 to TCM-433).
How should this be manually tested?
Go to this Workspace and do any action related to content or style, this action will be caught and sent to Redshift where it is going to be disposed like this on its GUI
or like this if you export the data as a JSON file
It is important to notice that these events will not be shown on Redshift in real time.
Screenshots or example usage
Type of changes
Notes
How does this PR make you feel? 🔗
![](put .gif link here - can be found under "advanced" on giphy)