Skip to content
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

Merged
merged 11 commits into from
Sep 9, 2024
Merged

[TCM-417] Integrate Site Editor with Audit app #467

merged 11 commits into from
Sep 9, 2024

Conversation

carolvalenca
Copy link
Contributor

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
Screenshot 2024-06-11 at 10 29 59
or like this if you export the data as a JSON file

[
  {
    "account_name": "plannerdev",
    "date": "2024-06-08 01:02:53+00",
    "operation": "copy binding content",
    "subject_id": "",
    "author_id": "276ba720-2b3b-4135-9439-ccafd202482f",
    "application": "cms",
    "batch_id": "2024_06_08_01",
    "id": "ef7604f1-849f-46e1-b4b9-e853b69a4c88",
    "entity_name": "binding",
    "entity_before_action": "\"\"",
    "entity_after_action": "\"\""
  }
]

It is important to notice that these events will not be shown on Redshift in real time.

Screenshots or example usage

Type of changes

✔️ Type of Change
_ Bug fix
✔️ New feature
_ Breaking change
_ Technical improvements

Notes

How does this PR make you feel? 🔗

![](put .gif link here - can be found under "advanced" on giphy)

Copy link
Contributor

vtex-io-ci-cd bot commented Jun 12, 2024

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:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link

vtex-io-docs-bot bot commented Jun 12, 2024

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

manifest.json Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@victorhmp victorhmp left a 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

CHANGELOG.md Outdated Show resolved Hide resolved
@carolvalenca carolvalenca merged commit b69ca4b into master Sep 9, 2024
1 check passed
Copy link
Contributor

vtex-io-ci-cd bot commented Sep 9, 2024

Your PR has been merged! App is being published. 🚀
Version 4.55.1 → 4.56.0

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:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

@carolvalenca carolvalenca restored the dev branch September 9, 2024 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants