You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deprecate legacy TF module variables for OUs (#94)
* Deprecate legacy TF module variables for OUs
DEPRECATION NOTICE
-------------------
Deprecating the following variables from all modules :-
- organizational_unit_ids
- org_units
With this breaking change, above legacy vars will no longer be supported for Secure installs.
Recommended Solutions
-----------------------
- For new Foundational installs: Users will need to use the new vars for including and excluding
organizational_units and/or accounts.
- For existing installs:
- It is highly recommended to migrate to using new variables. Please work with Sysdig to migrate
your Terraform installs to use new vars instead to achieve the same deployment outcome.
- Pin and use older module version if you do not wish to migrate.
* Update test files
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ There are four new parameters to configure organizational deployments on the clo
73
73
3.`include_accounts` - List of AWS Accounts to deploy the Sysdig Secure for Cloud resources in.
74
74
4.`exclude_accounts` - List of AWS Accounts to exclude deploying the Sysdig Secure for Cloud resources in.
75
75
76
-
**WARNING**: module variable`organizational_unit_ids` / `org_units`will be DEPRECATED on 30th November, 2025. Please work with Sysdig to migrate your Terraform installs to use `include_ouids` instead to achieve the same deployment outcome.
76
+
**DEPRECATION NOTICE**: module variables`organizational_unit_ids` / `org_units`have been DEPRECATED and are no longer supported. Please work with Sysdig to migrate your Terraform installs to use `include_ouids` instead to achieve the same deployment outcome.
Copy file name to clipboardExpand all lines: modules/agentless-scanning/README.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,6 @@ No modules.
62
62
| <aname="input_kms_key_deletion_window"></a> [kms\_key\_deletion\_window](#input\_kms\_key\_deletion\_window)| Deletion window for shared KMS key |`number`|`7`| no |
63
63
| <aname="input_mgt_stackset"></a> [mgt\_stackset](#input\_mgt\_stackset)| (Optional) Indicates if the management stackset should be deployed |`bool`|`true`| no |
64
64
| <aname="input_name"></a> [name](#input\_name)| The name of the installation. Assigned to most child resource(s) |`string`|`"sysdig-secure-scanning"`| no |
65
-
| <aname="input_org_units"></a> [org\_units](#input\_org\_units)| TO BE DEPRECATED on 30th November, 2025: Please work with Sysdig to migrate to using `include_ouids` instead.<br>(Optional) List of Organization Unit IDs in which to setup Agentless Scanning. By default, Agentless Scanning will be setup in all accounts within the Organization. This field is ignored if `is_organizational = false`|`set(string)`|`[]`| no |
66
65
| <aname="input_regions"></a> [regions](#input\_regions)| (Optional) List of regions in which to install Agentless Scanning |`set(string)`|`[]`| no |
67
66
| <aname="input_scanning_account_id"></a> [scanning\_account\_id](#input\_scanning\_account\_id)| The identifier of the account that will receive volume snapshots |`string`|`"878070807337"`| no |
68
67
| <aname="input_stackset_admin_role_arn"></a> [stackset\_admin\_role\_arn](#input\_stackset\_admin\_role\_arn)| (Optional) stackset admin role to run SELF\_MANAGED stackset |`string`|`""`| no |
# As per https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html#organization-structure, there can be only one root
condition=length(var.org_units) ==0# if this condition is false we throw warning
29
-
error_message=<<-EOT
30
-
WARNING: TO BE DEPRECATED 'org_units' on 30th November, 2025. Please work with Sysdig to migrate your Terraform installs to use 'include_ouids' instead.
31
-
EOT
32
-
}
33
-
34
-
assert {
35
-
condition=!local.both_org_configuration_params# if this condition is false we throw error
36
-
error_message=<<-EOT
37
-
ERROR: If both org_units and include_ouids/exclude_ouids/include_accounts/exclude_accounts variables are populated,
38
-
ONLY org_units will be considered. Please use only one of the two methods.
39
-
40
-
Note: org_units is going to be DEPRECATED on 30th November, 2025. Please work with Sysdig to migrate your Terraform installs.
Copy file name to clipboardExpand all lines: modules/agentless-scanning/variables.tf
-10Lines changed: 0 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -30,16 +30,6 @@ variable "is_organizational" {
30
30
default=false
31
31
}
32
32
33
-
variable"org_units" {
34
-
description=<<-EOF
35
-
TO BE DEPRECATED on 30th November, 2025: Please work with Sysdig to migrate to using `include_ouids` instead.
36
-
When set, list of Organization Unit IDs to setup Agentless Scanning. By default, Agentless Scanning will be setup in all accounts within the Organization.
37
-
This field is ignored if `is_organizational = false`
38
-
EOF
39
-
type=set(string)
40
-
default=[]
41
-
}
42
-
43
33
variable"regions" {
44
34
description="(Optional) List of regions in which to install Agentless Scanning"
| <aname="input_failure_tolerance_percentage"></a> [failure\_tolerance\_percentage](#input\_failure\_tolerance\_percentage)| The percentage of accounts, per Region, for which stack operations can fail before AWS CloudFormation stops the operation in that Region |`number`|`90`| no |
54
54
| <aname="input_is_organizational"></a> [is\_organizational](#input\_is\_organizational)| true/false whether secure-for-cloud should be deployed in an organizational setup (all accounts of org) or not (only on default aws provider account) |`bool`|`false`| no |
55
-
| <aname="input_org_units"></a> [org\_units](#input\_org\_units)| TO BE DEPRECATED on 30th November, 2025: Please work with Sysdig to migrate to using `include_ouids` instead.<br>Org unit id to install cspm |`set(string)`|`[]`| no |
56
55
| <aname="input_region"></a> [region](#input\_region)| Default region for resource creation in organization mode |`string`|`""`| no |
57
56
| <aname="input_tags"></a> [tags](#input\_tags)| sysdig secure-for-cloud tags. always include 'product' default tag for resource-group proper functioning |`map(string)`| <pre>{<br> "product": "sysdig-secure-for-cloud"<br>}</pre> | no |
58
57
| <aname="input_timeout"></a> [timeout](#input\_timeout)| Default timeout values for create, update, and delete operations |`string`|`"30m"`| no |
# As per https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html#organization-structure, there can be only one root
condition=length(var.org_units) ==0# if this condition is false we throw warning
29
-
error_message=<<-EOT
30
-
WARNING: TO BE DEPRECATED 'org_units' on 30th November, 2025. Please work with Sysdig to migrate your Terraform installs to use 'include_ouids' instead.
31
-
EOT
32
-
}
33
-
34
-
assert {
35
-
condition=!local.both_org_configuration_params# if this condition is false we throw error
36
-
error_message=<<-EOT
37
-
ERROR: If both org_units and include_ouids/exclude_ouids/include_accounts/exclude_accounts variables are populated,
38
-
ONLY org_units will be considered. Please use only one of the two methods.
39
-
40
-
Note: org_units is going to be DEPRECATED on 30th November, 2025. Please work with Sysdig to migrate your Terraform installs.
0 commit comments