How to use inline credentials instead of .ftppass

[TanKucukhas]

Documentation says

Usernames and passwords can be stored in an optional JSON file (.ftppass in the project folder or optionaly defined inauthPath).

But does not mention anything about to be able to use inline credentials, is there a way I could do that?

This does not seems to work still asks password on the console

auth: {
                    host: '<%= settings.user.ftpHost %>',
                    port: '<%= settings.user.ftpPort %>',
                    authKey: {
                            "username": "username",
                            "password": "password"
                    }
                }

[zonak]

The idea is to have a way to store them in a file that you can exclude from version control or provide them as parameters when you are executing the task. The file doesn't go through any tempting so ... no, you cannot use it as in the example.

[TanKucukhas]

I understand it has to be in a separate file for exclusion purposes but in my case I have a global credentials file that includes other passwords like SMTP and I just don't want to .ftppass sitting there alone only for ftp configuration.

So instead of .ftppass I was using a global file that has all of the passwords called .creds. but this is not working for ftp-deploy.

{
  "ftp": {
    "username": "ftp-user",
    "password": "ftp-password"
  },
  "gmail": {
    "type": "SMTP",
    "username": "user@gmail.com",
    "password": "userpass"
  }
}

[TanKucukhas]

May be use a more global name for the .ftppass file like .credentials or .pass? That way I could put my other passwords as well and I don't have to have separate passwords for each plugin.

[julkue]

@TanKucukhas have a look at the way it is implemented in jmBoilerplate. The .ftppass file will be generated by arguments from the console.

[zonak]

@julmot's approach is one way to go. Also the task has the ability to accept parameters from cli as well.
Please understand that satisfying everyone's custom use cases is going to make maintenance much harder than it has to be.