[GitHub] Issues Datastream

[kcreddy]

What does this PR do?

Adds Issues datastream to Github package. With this users can ingest issues created across all repositories in an organisation or for specific repository.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Pipeline Tests

• elastic-package stack down && elastic-package build && elastic-package stack up --version=8.6.0 -d -v --services=elasticsearch && eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate --data-streams issues

Run pipeline tests for the package
--- Test results for package: github - START ---
╭─────────┬─────────────┬───────────┬─────────────────────────────┬────────┬──────────────╮
│ PACKAGE │ DATA STREAM │ TEST TYPE │ TEST NAME                   │ RESULT │ TIME ELAPSED │
├─────────┼─────────────┼───────────┼─────────────────────────────┼────────┼──────────────┤
│ github  │ issues      │ pipeline  │ test-github-issues-json.log │ PASS   │    31.8455ms │
╰─────────┴─────────────┴───────────┴─────────────────────────────┴────────┴──────────────╯
--- Test results for package: github - END   ---
Done

System Tests

• elastic-package stack down && elastic-package build && elastic-package stack up --version=8.6.0 -d -v --services=elasticsearch && eval "$(elastic-package stack shellinit)" && elastic-package test system --generate --data-streams issues

Run system tests for the package
2023/02/16 15:00:38  INFO Write container logs to file: /Users/kcreddy/go/src/github.com/elastic/integrations/build/container-logs/github-1676539838164054000.log
--- Test results for package: github - START ---
╭─────────┬─────────────┬───────────┬───────────┬────────┬───────────────╮
│ PACKAGE │ DATA STREAM │ TEST TYPE │ TEST NAME │ RESULT │  TIME ELAPSED │
├─────────┼─────────────┼───────────┼───────────┼────────┼───────────────┤
│ github  │ issues      │ system    │ default   │ PASS   │ 26.937829917s │
╰─────────┴─────────────┴───────────┴───────────┴────────┴───────────────╯
--- Test results for package: github - END   ---
Done

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-02-21T08:09:18.973+0000

• Duration: 17 min 6 sec

Test stats 🧪

Test	Results
Failed	0
Passed	34
Skipped	0
Total	34

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (5/5)	💚
Files	100.0% (5/5)	💚
Classes	100.0% (5/5)	💚
Methods	100.0% (64/64)	💚
Lines	93.833% (989/1054)	👍 8.028
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[P1llus]

Feel free to modify based on comment above before merging, good job! 👍

[elasticmachine]

Package github - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=github