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
The webhook `secret` is supplied inside the `config` map but Forgejo,
like Gitea, treats it as write-only: it is accepted on create/update
but never returned by the API. The provider previously rebuilt `config`
wholesale from the API response in `from()`, dropping the `secret` key.
The planned `config` therefore differed from the applied `config`,
failing Terraform's post-apply consistency check with "Provider produced
inconsistent result after apply ... inconsistent values for sensitive
attribute".
Mirror the existing write-only handling (`authorization_header`,
`branch_filter`) by carrying known write-only config keys over from the
prior plan/state value when mapping the API response into state.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
## Unreleased
2
+
3
+
BUG FIXES:
4
+
5
+
-`forgejo_repository_webhook`: Preserve write-only `config.secret` from configuration so managing the webhook secret no longer causes "Provider produced inconsistent result after apply"
0 commit comments