Path reading incompatibility between DSL and Fabric

Description

Using cloudify-fabric-plugin v2.0.4 on a v4.6 manager
When setting a key path in a blueprint "~/.ssh/key.pem" the DSL reads it correctly and even warn that it is not advised to use this way anymore
`You have requested to save the private key to /etc/cloudify/.ssh/key.pem. You are strongly discouraged from saving private keys to the file system. This feature is currently supported...`
When Fabric tries to get the key it fails on

Although the file is there and accessible to cfyuser.

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1.
2.
3.

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Activity

Show:
Michael Glokhman
September 21, 2020, 2:14 PM
Edited

Tested on 4.6

paramiko, which is used by the fabric plugin, doesn’t support ~ in file paths. A full path needs to be provided.
Docs updated accordingly.

Jonathan Abramsohn
September 22, 2020, 10:15 AM

It was supported in old versions of Paramiko, therefore might create backward incompatibility with older versions of fabric plugin.

+We should have consistency between DSL and plugins, if it is accepted by DSL, it should also be the same for plugins and vice versa.

Alex Molev
September 22, 2020, 11:18 AM

not sure what do you mean by accepted by DSL

the type of the parameter is a string, so any valid string will be acceptable

Assignee

Michael Glokhman

Reporter

Jonathan Abramsohn

Severity

Medium

Target Version

5.1

Premium Only

no

Found In Version

4.6

QA Owner

None

Bug Type

regression bug

Customer Encountered

Yes

Customer Name

c311

Release Notes

yes

Priority

None

Priority

Medium
Configure