Skip to content

[b/551874614] Migration of IBM_SECURITY_VERIFY_SAAS logtype from Piper workspace to github - #1186

Open
shridharn-stack wants to merge 1 commit into
mainfrom
chanduc_synthetic_migration_ibm_security_verify_saas
Open

[b/551874614] Migration of IBM_SECURITY_VERIFY_SAAS logtype from Piper workspace to github#1186
shridharn-stack wants to merge 1 commit into
mainfrom
chanduc_synthetic_migration_ibm_security_verify_saas

Conversation

@shridharn-stack

Copy link
Copy Markdown
Contributor

Description : The purpose of this migration is to establish a community Git repository that enables customer-driven parser updates. Customers will be able to pull the codebase, make modifications, and submit their changes for review and approval by the CBN team.

Log_types:

  1. IBM_SECURITY_VERIFY_SAAS

Checklist:

Please ensure you have completed the following items before submitting your PR. This helps us review your contribution faster and more efficiently.

General Checks:

  • I have read and followed the project's contributing.md guide.
  • My code follows the project's coding style guidelines.
  • I have performed a self-review of my own code.
  • My changes do not introduce any new warnings.
  • My changes pass all existing tests.
  • I have added new tests where appropriate to cover my changes. (If applicable)
  • I have updated the documentation where necessary (e.g., README, API docs). (If applicable)

Open-Source Specific Checks:

  • My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
  • My changes do not expose any internal-only code examples, configurations, or URLs.
  • All code examples, comments, and messages are generic and suitable for a public repository.
  • I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

  • I have included the Buganizer ID in the PR title or description (e.g., "Internal Buganizer ID: 123456789" or "Related Buganizer: go/buganizer/123456789").
  • I have ensured that all internal discussions and PII related to this work remain in Buganizer.
  • I have tagged the PR with one or more labels that reflect the pull request purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Parser Validations Parser parser-migration To be used for all piper logtype migrations to github

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants