feat(secure): deprecate sysdig_secure_posture_zone in favor of sysdig_secure_zone#722
Merged
tembleking merged 2 commits intomasterfrom Apr 7, 2026
Merged
feat(secure): deprecate sysdig_secure_posture_zone in favor of sysdig_secure_zone#722tembleking merged 2 commits intomasterfrom
tembleking merged 2 commits intomasterfrom
Conversation
…_secure_zone The CSPM v1 API used by sysdig_secure_posture_zone does not support resourceGroupId for the IBM target type, returning a 400 error. Rather than working around v1 limitations, deprecate the resource and guide users to sysdig_secure_zone which uses the Platform Zones API with full IBM support. Ref: ET-818
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request deprecates the sysdig_secure_posture_zone resource and data source in favor of sysdig_secure_zone. The CSPM v1 API used by the deprecated resource does not support resourceGroupId for IBM target types, so users are being guided to migrate to the Platform Zones API which has full IBM support. The PR adds deprecation messages to the code, deprecation notices to the documentation, and provides a comprehensive migration guide.
Changes:
- Added
DeprecationMessageto both the resource and data source definitions - Added deprecation notices to resource and data source documentation
- Added a detailed migration guide to
sysdig_secure_zonedocumentation with state migration steps and scope mapping examples - Documented the
policy_idslimitation (the new resource does not manage policy assignments)
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| sysdig/resource_sysdig_secure_posture_zone.go | Added DeprecationMessage to resource schema |
| sysdig/data_source_sysdig_secure_posture_zone.go | Added DeprecationMessage to data source schema |
| website/docs/r/secure_posture_zone.md | Added deprecation warning banner |
| website/docs/d/secure_posture_zone.md | Added deprecation warning banner |
| website/docs/r/secure_zone.md | Added comprehensive migration guide with 4-step migration process |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
alecron
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The CSPM v1 API used by
sysdig_secure_posture_zonedoes not supportresourceGroupIdfor the IBM target type, returning a 400 error. Rather than working around v1 limitations, this deprecates the resource and guides users tosysdig_secure_zonewhich uses the Platform Zones API with full IBM support.DeprecationMessagetosysdig_secure_posture_zoneresource and data sourcesysdig_secure_zonedocumentation covering scope mapping, state migration, andpolicy_idslimitation