From 4a0e98bab81fd65f08a719066f0425f8f9fd81ed Mon Sep 17 00:00:00 2001 From: Nathan Coad Date: Mon, 8 Apr 2024 13:59:00 +1000 Subject: [PATCH] test secure ftp --- .drone.yml | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.drone.yml b/.drone.yml index d33487a..a6257d2 100644 --- a/.drone.yml +++ b/.drone.yml @@ -93,7 +93,7 @@ steps: FTP_PASSWORD: from_secret: FTP_PASSWORD PLUGIN_HOSTNAME: ftp.emc.com:21 - PLUGIN_SECURE: false + PLUGIN_SECURE: true PLUGIN_VERIFY: false PLUGIN_CHMOD: false #PLUGIN_DEBUG: false diff --git a/README.md b/README.md index 58f9d9c..08edda1 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ WantedBy=multi-user.target ``` ## API Usage -API calls should return http status code of **200** if successful, or **4xx** if unsuccessful. API calls that are unsuccessful will also include a JSON response with the key `error` and a value of the reason for the failure. Successful API calls will include a `message` key with a value of either success or something more detailed such as "user deletion success" +API calls return http status code of **200** if successful, or **4xx** if unsuccessful. API calls that are unsuccessful will also include a JSON response with the key `error` and a value of the reason for the failure. Successful API calls will include a `message` key with a value of either success or something more detailed such as "user deletion success" API calls that create or modify a record will include the created/updated record in the JSON response.