Skip to content

adds support for require replace when updating a field in campaign resource#2760

Merged
aditya-okta merged 2 commits into
masterfrom
fix/issue-2527
Apr 6, 2026
Merged

adds support for require replace when updating a field in campaign resource#2760
aditya-okta merged 2 commits into
masterfrom
fix/issue-2527

Conversation

@aditya-okta
Copy link
Copy Markdown
Contributor

@aditya-okta aditya-okta commented Mar 29, 2026

fixes #2527 , fixes #2738
The PR adds functionality to force replacement of the resource i.e destroy and recreate the resource with the updated fields.

@aditya-okta aditya-okta marked this pull request as ready for review April 3, 2026 12:07
@github-actions github-actions Bot requested a review from dhiwakar-okta April 3, 2026 12:07
"Update Not Supported",
"No other fields other than launch_campaign and end_campaign are updatable for this resource. Terraform will retain the existing state.",
"The okta_campaign resource does not support in-place updates. All attributes require replacement. "+
"If you see this error, ensure all campaign attributes have 'requires replacement' plan modifiers, "+
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is an error that would be seen by the customer right ?

Copy link
Copy Markdown
Contributor

@dhiwakar-okta dhiwakar-okta left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@aditya-okta aditya-okta merged commit ef33280 into master Apr 6, 2026
4 checks passed
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.

okta_campaign: support updating reviewer_settings or mark as requires_replace Unexpected behaviour with okta_campaign resource

2 participants