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
Consider supporting pause/unpause and disable/enable resources (sources, destinations, connections).
Use case: when developers want to deploy new resources but are not ready for them to be active yet (Slack reference).
There are 2 main issues with this feature.
The first issue is how to implement this on a technical level. Hookdeck resources cannot toggle these settings (pause status, enabled status) via normal POST / PUT requests from CRUD endpoints. Instead, there are dedicated endpoints for this purpose. This is a bit "anti-Terraform" as Terraform is dedicated to handling CRUD operations. To support this behavior, we may need to customize the Terraform flow further to make extra API calls to accomplish this. That would also complicate things a bit as it will be difficult to accomplish atomicity within the flow.
The second issue is related to UX (or DX). These toggles are mostly handled on the dashboard by developers manually setting things up and making changes. If not handled carefully, developers may update states that are best handled by Terraform and lead to unexpected and/or undesired behavior.
The text was updated successfully, but these errors were encountered:
Consider supporting pause/unpause and disable/enable resources (sources, destinations, connections).
Use case: when developers want to deploy new resources but are not ready for them to be active yet (Slack reference).
There are 2 main issues with this feature.
The first issue is how to implement this on a technical level. Hookdeck resources cannot toggle these settings (pause status, enabled status) via normal POST / PUT requests from CRUD endpoints. Instead, there are dedicated endpoints for this purpose. This is a bit "anti-Terraform" as Terraform is dedicated to handling CRUD operations. To support this behavior, we may need to customize the Terraform flow further to make extra API calls to accomplish this. That would also complicate things a bit as it will be difficult to accomplish atomicity within the flow.
The second issue is related to UX (or DX). These toggles are mostly handled on the dashboard by developers manually setting things up and making changes. If not handled carefully, developers may update states that are best handled by Terraform and lead to unexpected and/or undesired behavior.
The text was updated successfully, but these errors were encountered: