Skip to content

feat(response actions) Support added#680

Merged
fcracker79 merged 15 commits intomasterfrom
feat/mirko/response-actions
Dec 10, 2025
Merged

feat(response actions) Support added#680
fcracker79 merged 15 commits intomasterfrom
feat/mirko/response-actions

Conversation

@fcracker79
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Member

@tembleking tembleking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am missing some documentation updates

@jose-pablo-camacho
Copy link
Copy Markdown
Contributor

I am missing some documentation updates

@tembleking, the documentation regarding these resources is outdated and @fcracker79 is contributing to it since it's working on a new feature change. Would it be ok to merge this and I can create a ticket to work and update the documentation regarding the onboarding's team resources? Please let me know.

@tembleking
Copy link
Copy Markdown
Member

@jose-pablo-camacho my concern is that we are updating the resources without modifying the documentation for each:
secure_cloud_auth_account and secure_cloud_auth_account_component

@fcracker79
Copy link
Copy Markdown
Contributor Author

@tembleking I've added some documentation.

@tembleking tembleking requested a review from Copilot December 10, 2025 15:22
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for AWS Response Actions in Sysdig Secure Cloud Authentication by introducing two new component types: COMPONENT_CLOUD_RESPONDER and COMPONENT_CLOUD_RESPONDER_ROLES. These components enable automated response capabilities through Lambda functions and IAM roles.

Key Changes:

  • Added schema definitions for cloud responder metadata fields
  • Implemented support for response actions feature and its components in account resources
  • Added comprehensive documentation with usage examples for the new component types

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
sysdig/common.go Adds schema constant definitions for cloud responder metadata and response actions feature
sysdig/resource_sysdig_secure_cloud_auth_account.go Implements response actions feature support including schema definitions, component construction, and resource data mapping
sysdig/resource_sysdig_secure_cloud_auth_account_component.go Adds metadata handling for cloud responder components in component-specific resource
sysdig/resource_sysdig_secure_cloud_auth_account_test.go Adds acceptance test for AWS response actions configuration
website/docs/r/secure_cloud_auth_account.md Documents the response actions feature with usage examples
website/docs/r/secure_cloud_auth_account_component.md Documents cloud responder component types with configuration examples

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread sysdig/resource_sysdig_secure_cloud_auth_account_test.go Outdated
Comment thread sysdig/resource_sysdig_secure_cloud_auth_account_test.go
Comment thread sysdig/resource_sysdig_secure_cloud_auth_account_test.go Outdated
Comment thread sysdig/resource_sysdig_secure_cloud_auth_account_test.go Outdated
fcracker79 and others added 3 commits December 10, 2025 16:28
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@fcracker79 fcracker79 merged commit 71269f0 into master Dec 10, 2025
22 checks passed
@fcracker79 fcracker79 deleted the feat/mirko/response-actions branch December 10, 2025 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants