Bug #39175
closed
Cloning a locked webhook template via Hammer creates a locked clone
Description
Description of problem:
When a locked webhook template is cloned using Hammer, the cloned template remains locked.
However, when the same locked webhook template is cloned via the Web UI, the cloned template is created in an unlocked state.
This results in inconsistent behavior between Hammer and the UI.
How reproducible:
Always
Is this issue a regression from an earlier version:*
No
Steps to Reproduce:
Identify an existing locked webhook template.
Clone the template using Hammer:
Actual behavior:
The cloned webhook template is created as locked when cloned via Hammer.
Expected behavior:
The cloned webhook template should be unlocked
Business Impact / Additional info:
Requires manual unlocking of templates cloned via Hammer.
Breaks parity between CLI and UI behavior.
Impacts automation and scripted workflows.
Updated by The Foreman Bot 5 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_webhooks/pull/98 added
Updated by Oleh Fedorenko 5 months ago
- Related to Bug #39176: Can't clone locked Partition table in API added
Updated by Oleh Fedorenko 5 months ago
- Related to Bug #39173: Cloning a locked report template via Hammer creates a locked clone added
Updated by Lukáš Hellebrandt 4 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_webhooks|8d4fba632b971af7681332423662107f5b115874.