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?
Activity
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.
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.
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
Reporter
Severity
Target Version
Premium Only
Found In Version
QA Owner
Bug Type
Customer Encountered
Customer Name
Release Notes
Priority
Epic Link
Priority
