cloudify-cosmo / cloudify-cli Goto Github PK

View Code? Open in Web Editor NEW

42.0 35.0 47.0 26.61 MB

Cloudify's CLI

License: Apache License 2.0

Python 99.30% Shell 0.35% Inno Setup 0.07% PowerShell 0.18% HCL 0.11%

cloudify-cli's Introduction

Cloudify CLI

Cloudify's Command Line Interface.

Usage

See Cloudify CLI

cloudify-cli's People

Contributors

Stargazers

Watchers

cloudify-cli's Issues

Blueprint upload fails with 'str' object does not support item assignment

Environment: macOS Monterey 12.3.1
Python: 3.7.13 via homebrew
Cloudify CLI:

cfy --version
Premium edition

Cloudify CLI 6.3.2
Cloudify Manager 6.4.0.dev1 [ip=8....app.cloudify.co]

I've tried uploading a blueprint that is valid and uploads successfully via GUI, but when I try running: cfy blueprints upload -b test-lz-blueprint -n landing-zone.yaml demo.tgz, i get an error that reads: 'str' object does not support item assignment

I also tried uploading the blueprint by referencing the yaml file directly, but I receive the same error message.

cloudify-cli has logs? this task has run tens minutes. how can i know if it is pending?

2014-12-25 02:44:31 CFY [manager_52301.creation] Task started 'cloudify_cli.bootstrap.tasks.creation_validation'

Work with cloudify-cli on MacOs

Hi,
I can't understand how to install / work with the cli on my mac os..can anyone please help me..
i got cloned the repo localy..how should i proceed from there?

Thanks a lot for your help!
Yishai.

Cloudify CLI stores user password in plaintext

When a user's profile is saved, it dumps the yaml profile settings into plaintext;

cloudify-cli/cloudify_cli/env.py

Lines 493 to 506 in 2fd55e0

 def save(self, destination=None): 

 if not self.profile_name: 

 raise CloudifyCliError('No profile name or Manager IP set') 

 workdir = destination or self.workdir 

 # Create a new file 

 if not os.path.exists(workdir): 

 os.makedirs(workdir) 

 target_file_path = os.path.join( 

 workdir, 

 constants.CLOUDIFY_PROFILE_CONTEXT_FILE_NAME) 

 with open(target_file_path, 'w') as f: 

 f.write(yaml.dump(self))

This presents a security risk on shared systems, with multiple users.

Executions without manager are executing code on localhost, not in the newly created instance

Description

When using cloudify CLI with local parameter like in this example : cfy local execute --workflow install --task-retries=10 --task-retry-interval=10, using for example this blueprint cloudify-nodecellar-docker-example > aws-ec2-blueprint.yaml or cloudify-nodecellar-example > aws-ec2-blueprint.yaml are executed in local machine where the command is launched and not in the remote machine where should be launched.
Of course, maybe 'local' means to work only and exclusivelly in local enviroment, but then, Why using amazon aws plugin works and deploys everything where should be except scripts or containers?

Other case

cloudify-nodecellar-example issue which reproduces the failure issues/99

Versions

Cloudify cli : 3.4.1
Docker plugin: 1.3.2
Docker: 1.11.2

Installation of the CLI is not working on Ubuntu 20.04

With the deb package:

sudo dpkg -i cloudify-cli_5.1.1-ga_amd64.deb 
[sudo] password for nico: 
Selecting previously unselected package cloudify.
(Reading database ... 196562 files and directories currently installed.)
Preparing to unpack cloudify-cli_5.1.1-ga_amd64.deb ...
Unpacking cloudify (5.1.1) ...
dpkg: dependency problems prevent configuration of cloudify:
 cloudify depends on python3 (<< 3.7); however:
  Version of python3 on system is 3.8.2-0ubuntu2.

dpkg: error processing package cloudify (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 cloudify

Then with pip, install ok. (in a pipx venv)

pipx install cloudify
⚠️  Note: cfy was already on your PATH at /usr/bin/cfy
  installed package cloudify 20.3.3, Python 3.8.5
  These apps are now globally available
    - cfy
done! ✨ 🌟 ✨

Then when I run cfy

cfy
Traceback (most recent call last):
  File "/home/nico/.local/bin/cfy", line 5, in <module>
    from cloudify_cli.main import _cfy
  File "/home/nico/.local/pipx/venvs/cloudify/lib/python3.8/site-packages/cloudify_cli/main.py", line 18, in <module>
    from .cli import cfy
  File "/home/nico/.local/pipx/venvs/cloudify/lib/python3.8/site-packages/cloudify_cli/cli/cfy.py", line 21, in <module>
    import StringIO
ModuleNotFoundError: No module named 'StringIO'

Cannot install docker plugin

Hi, I'm using an vagrant ubuntu image, and installed cloudify 3.3.1 by sudo python get-cloudify.py.

When I tried to run cfy local init --install-plugins -p singlehost-blueprint.yaml described in cloudify-nodecellar-docker-example, I got an error message: You must be running inside a virtualenv to install blueprint plugins. However, I'm inside a virtual env(vagrant ubuntu).

If I run cfy local init -p singlehost-blueprint.yaml without --install-plugins, I got another error message: mapping error: No module named docker_plugin.tasks.

Any ideas/workarounds?

	def save(self, destination=None):
	if not self.profile_name:
	raise CloudifyCliError('No profile name or Manager IP set')

	workdir = destination or self.workdir
	# Create a new file
	if not os.path.exists(workdir):
	os.makedirs(workdir)
	target_file_path = os.path.join(
	workdir,
	constants.CLOUDIFY_PROFILE_CONTEXT_FILE_NAME)

	with open(target_file_path, 'w') as f:
	f.write(yaml.dump(self))