saltstack-autoscaling | A SaltStack AWS autoscaling example skeleton

by JensRantil Python Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | saltstack-autoscaling Summary

saltstack-autoscaling is a Python library. saltstack-autoscaling has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However saltstack-autoscaling build file is not available. You can download it from GitHub.

I was unable to make the original sqs_engine engine that came with the SaltStack project to work. This was probably mostly due to the fact that I was using an older version of boto, version 2.2.2, which didn’t support role based authentication, nor custom long-polling timeouts. I was also having issues with JSON decoding. That’s why this repository ships with its own engine. I’ll see if I can get any of my changes merged upstream.

Support

Quality

Security

License

Reuse

Support

saltstack-autoscaling has a low active ecosystem.

It has 16 star(s) with 3 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 3 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of saltstack-autoscaling is current.

Quality

saltstack-autoscaling has 0 bugs and 0 code smells.

Security

saltstack-autoscaling has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

saltstack-autoscaling code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

saltstack-autoscaling is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

saltstack-autoscaling releases are not available. You will need to build from source code and install.

saltstack-autoscaling has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are available. Examples and code snippets are not available.

saltstack-autoscaling saves you 133 person hours of effort in developing the same functionality from scratch.

It has 334 lines of code, 32 functions and 3 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed saltstack-autoscaling and discovered the below as its top functions. This is intended to give you an instant insight into saltstack-autoscaling implemented functionality, and help decide if they suit your requirements.

Start a SQS queue
Get a connection to SQS
Acquire the lock

Get all kandi verified functions for this library.

saltstack-autoscaling Key Features

No Key Features are available at this moment for saltstack-autoscaling.

saltstack-autoscaling Examples and Code Snippets

No Code Snippets are available at this moment for saltstack-autoscaling.

Community Discussions

No Community Discussions are available at this moment for saltstack-autoscaling.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install saltstack-autoscaling

Search and replace all PLACEHOLDER* constants. See below for descriptions. See README files in individual directories for details on where files need to go.
PLACEHOLDER_AUTOSCALING_SQS_QUEUE: The name of the SQS queue that auto scaling events are published to.
PLACEHOLDER_MINION_PREFIX: The prefix of the autoscaled minions. Could be "myworker" if you have a bunch of workers that are being autoscaled.
PLACEHOLDER_MY_AWS_REGION: The AWS region where your SQS queue lives.
PLACEHOLDER_PATH_TO_REACTORS: The directory where you keep you reactors in the file system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: