feat(crowdstrike): CrowdStrike source plugin#5122
Conversation
plugins/source/crowdstrike/resources/services/incidents/crowdscore_fetch.go
Outdated
Show resolved
Hide resolved
disq
left a comment
There was a problem hiding this comment.
Small things, also remove the codegen binary from codegen/ :)
plugins/source/crowdstrike/resources/services/incidents/crowdscore_fetch.go
Outdated
Show resolved
Hide resolved
plugins/source/crowdstrike/resources/services/alerts/query_fetch.go
Outdated
Show resolved
Hide resolved
erezrokah
left a comment
There was a problem hiding this comment.
Thanks for the PR @cqgaurav, not sure if this is meant to be released, but if it is, we should also follow https://www.notion.so/cloudquery/Adding-a-new-plugin-to-the-monorepo-f216b653dbe648b2b3512fb8d59a8f89
Co-authored-by: Kemal <223029+disq@users.noreply.github.com>
Co-authored-by: Kemal <223029+disq@users.noreply.github.com>
…core_fetch.go Co-authored-by: Kemal <223029+disq@users.noreply.github.com>
…ch.go Co-authored-by: Kemal <223029+disq@users.noreply.github.com>
|
@erezrokah Thanks for that link. Is it okay to break that into a separate pr to keep the example PR somewhat shorter ? |
@cqgaurav I'm not sure. Is this PR here to serve as an example on how to add a community plugin or a plugin to the monorepo? If for a community plugin I think we should discuss this a bit more, as we've had a template and also considered a scaffold command. If for the monorepo, I think it should include the parts that also release the plugin |
|
@erezrokah Yes, I don't have a strong opinion, and its possible that the users don't necessarily care about differentiating between plugin and releasing it separately. I added the requested changes |
This PR has the following changes to source plugin(s) tables:
|
🤖 I have created a release *beep* *boop* --- ## 1.0.0 (2022-12-20) ### Features * **crowdstrike:** CrowdStrike source plugin ([#5122](#5122)) ([0b6b47d](0b6b47d)) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.0 ([#5539](#5539)) ([fb71293](fb71293)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.2 ([#5583](#5583)) ([d721c4e](d721c4e)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.3 ([#5639](#5639)) ([6452d0e](6452d0e)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.4 ([#5649](#5649)) ([b4aa889](b4aa889)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.5 ([#5661](#5661)) ([b354b8a](b354b8a)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.6 ([#5790](#5790)) ([8e2663c](8e2663c)) * **deps:** Update module github.com/cloudquery/plugin-sdk to v1.12.7 ([#5797](#5797)) ([15da529](15da529)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Summary
This PR adds a few services for a crowdstrike cloudquery plugin. It is intended to serve as a smaller example for adding a realisting CQ plugin.
Tested using the following source and destination configs
cloudquery sync .// source.yml
Then start a local postgre in docker using
docker exec -it cloudquery_postgres psql -U postgresAnd test that the table was created.
Note: I haven't been able to test this end to end because of the complexity of a test CrowdStrike setup combined with a non existent crowdstrike support, but hopefully it should work as an example.