Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add org account mappings to Agentless for AWS #473

Merged
merged 2 commits into from
May 31, 2023

Conversation

wl-smith
Copy link
Contributor

@wl-smith wl-smith commented Apr 25, 2023

Issue: (https://lacework.atlassian.net/browse/RAIN-54797)

Description:
This is step #2 to provide LW Org support for Terraform integrations for Agentless. Step 1 having been to update go-sdk: lacework/go-sdk#1251.

Additional Info:
The changes made were essentially to add the account mapping file to the awsOrgAgentlessScanningIntegrationSchema in terraform, add helper functions to get & manipulate the account mapping input from the customer.

Tests:
Added a new integration test specifically for AwsSidekickOrg Integrations as well as updated the example terraform and the response object to get the AwsAgentlessOrgScanningResponse, which is a new function in integration.go that uses the LwOrgClient instead of the LwClient.

@wl-smith wl-smith force-pushed the add-org-account-mappings-to-awls branch 2 times, most recently from f208ce5 to c39e325 Compare May 8, 2023 18:51
@wl-smith wl-smith force-pushed the add-org-account-mappings-to-awls branch 3 times, most recently from 937201d to cb40e0d Compare May 25, 2023 16:33
@wl-smith wl-smith changed the title feat (RAIN-54797) Add org account mappings to Agentless for gcp & aws feat (RAIN-54797) Add org account mappings to Agentless for AWS May 25, 2023
@wl-smith wl-smith marked this pull request as ready for review May 25, 2023 16:46
@wl-smith wl-smith requested a review from a team as a code owner May 25, 2023 16:46
@wl-smith wl-smith force-pushed the add-org-account-mappings-to-awls branch 2 times, most recently from 7f7debc to 46d407f Compare May 25, 2023 18:43
@wl-smith wl-smith requested a review from ammarekbote May 25, 2023 20:48
@wl-smith wl-smith force-pushed the add-org-account-mappings-to-awls branch from 342f7b4 to ed75185 Compare May 30, 2023 15:06
@wl-smith wl-smith force-pushed the add-org-account-mappings-to-awls branch from 2505e90 to ea3bb24 Compare May 30, 2023 16:02
@afiune afiune changed the title feat (RAIN-54797) Add org account mappings to Agentless for AWS feat: Add org account mappings to Agentless for AWS May 30, 2023
Copy link
Contributor

@afiune afiune left a comment

Choose a reason for hiding this comment

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

Copy link
Contributor

@afiune afiune left a comment

Choose a reason for hiding this comment

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

@afiune
Copy link
Contributor

afiune commented May 30, 2023

CI failure is NOT related to this change.

@afiune afiune merged commit a80f2d3 into main May 31, 2023
@afiune afiune deleted the add-org-account-mappings-to-awls branch May 31, 2023 00:45
@lacework-releng lacework-releng mentioned this pull request Jun 2, 2023
afiune added a commit to lacework/terraform-aws-agentless-scanning that referenced this pull request Jun 15, 2023
The PR lacework/terraform-provider-lacework#473 introduced a new field named `org_account_mappings` which is only available from version `1.8.0` and above.

We made use of this new variable with PR #81 but we forgot to bump the min version, this causes potential issues like #83 where users might be using an older version of the Lacework provider that does not have this new field.

The fix is to update the version constraint to `~> 1.8`

Note: If you don't know about the pessimistic constraint, please read this doc; https://developer.hashicorp.com/terraform/language/expressions/version-constraints#version-constraint-syntax
afiune added a commit to lacework/terraform-aws-agentless-scanning that referenced this pull request Jun 15, 2023
The PR lacework/terraform-provider-lacework#473 introduced a new field named `org_account_mappings` which is only available from version `1.8.0` and above.

We made use of this new variable with PR #81 but we forgot to bump the min version, this causes potential issues like #83 where users might be using an older version of the Lacework provider that does not have this new field.

The fix is to update the version constraint to `~> 1.8`

Note: If you don't know about the pessimistic constraint, please read this doc; https://developer.hashicorp.com/terraform/language/expressions/version-constraints#version-constraint-syntax
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.

2 participants