[SIEMINT-76] [Release] [DDS] PingOne: Crawler Integration v1.0.0
What does this PR do?
This is a initial release PR of PingOne integration including all the required assets.
Additional Notes
- Crawler code for this integration has been committed in its respective repo
- Pipeline and Facet group created for this integration are available in our sandbox and would be shared separately with the required teams.
- Samples for the pipeline review would also be shared separately with the required teams.
- OOTB detection rules JSON would be shared separately with the required teams as a part of separate repository ..
- Since during the standard attribute remapping we are not preserving the source attributes as per suggested best practices, it would result in filters using these standard attributes populating the values of other integrations as well as per current Datadog behavior
Review checklist (to be filled by reviewers)
- [ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
- [ ] Changelog entries must be created for modifications to shipped code
- [ ] Add the
qa/skip-qalabel if the PR doesn't need to be tested during QA. - [ ] If you need to backport this PR to another branch, you can add the
backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged
Setting the assets/no-deploy flag on this until https://github.com/DataDog/integrations-core/pull/17870 merges
Thanks, created DOCS-8353 to review
Thanks for making the changes to the message remapper, everything looks good for the logs integration pipeline. Will approve after I can test in staging once this comment from @nathanmadams is resolved and the other PR is merged
The other PR just merged so I think you'll need to rebase this one. Once you do, feel free to remove the assets/no-deploy label so it can be reviewed.
@nathanmadams I have rebase the branch. But don't have permission to remove label: assets/no-deploy. Can you please update this?
@nathanmadams I have rebase the branch. But don't have permission to remove label:
assets/no-deploy. Can you please update this?
Just took care of it, I'll get this in staging and will approve after I can test it out
Just merged master to see if the validations would re-run successfully.
Does this PR look good to merge?
thank you!
@Wyrine Are we good to merge this PR after this change?
Are we good to merge this PR after this change?
Yes, good to merge!