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
Currently, the POST, PUT, and DELETE endpoints for secret imports respond with a success message (HTTP CODE 200). The proposed enhancement involves having these endpoints return an object containing the secretImport field, similar to the behavior of the GET endpoint.
Why would it be useful?
Aligning the response format of these endpoints with other CRUD resources, such as secrets, which return objects instead of plain messages, would provide consistency. Additionally, this change is essential for implementing a comprehensive terraform resource for secret-imports.
Additional context
I've initiated a draft PR in the terraform provider repository to facilitate the management of secret imports, which can be found here: Terraform Provider Infisical PR #26.
Feature Description
Currently, the POST, PUT, and DELETE endpoints for secret imports respond with a success message (HTTP CODE 200). The proposed enhancement involves having these endpoints return an object containing the
secretImport
field, similar to the behavior of the GET endpoint.Why would it be useful?
Aligning the response format of these endpoints with other CRUD resources, such as secrets, which return objects instead of plain messages, would provide consistency. Additionally, this change is essential for implementing a comprehensive terraform resource for secret-imports.
Additional context
I've initiated a draft PR in the terraform provider repository to facilitate the management of secret imports, which can be found here: Terraform Provider Infisical PR #26.
From SyncLinear.com | ENG-337
The text was updated successfully, but these errors were encountered: