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

Add specification for post event to an analytics collection #3363

Merged
merged 7 commits into from
Jan 4, 2025

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Dec 18, 2024

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🔴 0/18 18/18

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl changed the title Add specification for post even to an analytics collection Add specification for post event to an analytics collection Dec 19, 2024
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🔴 0/18 18/18

You can validate these APIs yourself by using the make validate target.

@l-trotta l-trotta self-assigned this Dec 19, 2024
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🔴 0/18 18/18

You can validate these APIs yourself by using the make validate target.

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🟢 18/18 18/18

You can validate these APIs yourself by using the make validate target.

1 similar comment
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🟢 18/18 18/18

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl mentioned this pull request Jan 3, 2025
65 tasks
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🟢 18/18 18/18

You can validate these APIs yourself by using the make validate target.

1 similar comment
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🟢 18/18 18/18

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl force-pushed the post-analytics-collection branch from bc083db to fc0037b Compare January 4, 2025 08:07
Copy link
Contributor

github-actions bot commented Jan 4, 2025

Following you can find the validation results for the APIs you have changed.

API Status Request Response
search_application.post_behavioral_analytics_event 🟢 18/18 18/18

You can validate these APIs yourself by using the make validate target.

@lcawl lcawl merged commit 2f57f6b into main Jan 4, 2025
7 checks passed
@lcawl lcawl deleted the post-analytics-collection branch January 4, 2025 08:13
github-actions bot pushed a commit that referenced this pull request Jan 4, 2025
Co-authored-by: Laura Trotta <[email protected]>
Co-authored-by: Quentin Pradet <[email protected]>
(cherry picked from commit 2f57f6b)
Copy link
Contributor

github-actions bot commented Jan 4, 2025

The backport to 8.17 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.17 8.17
# Navigate to the new working tree
cd .worktrees/backport-8.17
# Create a new branch
git switch --create backport-3363-to-8.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2f57f6bbe10648cf0b45a8b7ed6ea37cbecf1494
# Push it to GitHub
git push --set-upstream origin backport-3363-to-8.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.17

Then, create a pull request where the base branch is 8.17 and the compare/head branch is backport-3363-to-8.17.

lcawl pushed a commit that referenced this pull request Jan 4, 2025
…3431)

Co-authored-by: Laura Trotta <[email protected]>
Co-authored-by: Quentin Pradet <[email protected]>
(cherry picked from commit 2f57f6b)
lcawl added a commit that referenced this pull request Jan 4, 2025
Co-authored-by: Laura Trotta <[email protected]>
Co-authored-by: Quentin Pradet <[email protected]>
(cherry picked from commit 2f57f6b)
@lcawl
Copy link
Contributor Author

lcawl commented Jan 4, 2025

💚 All backports created successfully

Status Branch Result
8.17

Questions ?

Please refer to the Backport tool documentation

pquentin pushed a commit that referenced this pull request Jan 7, 2025
…3432)

Co-authored-by: Laura Trotta <[email protected]>
Co-authored-by: Quentin Pradet <[email protected]>
(cherry picked from commit 2f57f6b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants