denismo/devopsgears

Provides foundation for the source-control driven DevOps infrastructure where everything is represented and managed via files.

devopsgears's Issues

Implement "self" descriptors

Self descriptiors are files named "self" in folders. They are in yaml format (by default, if no extensions is specified) and describe the actual resource. When resource is registered, the resource description is read from "self" rather than from the file (because there is no file - it is a folder with the name of the resource).

Create on.finished event for handlers

Create handler for running anything within EC2 instance

Depends on #10

Resources need to have short and long names

Especially file resources, their unique name (aka ID) is their path. However their short name can be defined in yaml file

Sort resources during initial scan

Pass in AWS properties as part of configuration

Properties such as profile name or credentials, and have SQS handler use those properties (for some reason, it was not possible initially as connect_to_region does not accept many properties)

Need to handle resource state

Create a test for the EC2 instance repository

Recognize scheduled (cron) handlers

Reorganize README

1. README itself should only contain basic introductory information. Important is quick start, and links to examples
2. Put all other pages on Wiki

Create command line runner

Accepting only get-resource-attribute and get-resource-data for now

Implement wiring resource to parent resource

Ensure handlers run before resources for "activated" event

This is to allow the handlers to prepare the instance, for example, when "activated' is raised by an EC2 instance

Create interface for controlling resources

In particular, for controlling resource states. It should be possible to write "devopsgears transition /dev deactivate" which would deactivate the whole "dev" environment, which would in turn stop all its EC2 instances for example.

Create README

Correct handling of run action

Currently run action is invoked if a script fails to execute. Instead, run handlers should be registered for handler type, and whenever that handler needs to run, run handler will get invoked by default.

Implement new state machine

the new state machine with activate state

1. Activate - active state
2. activeByDefault resources
3. Root is active by default
4. When child attaches to parent which is active, its "activate" handler is immediately triggered

Add sorting of handlers (especially action handlers)

Handlers need to be sorted so that more specific handlers are executed before general. Only the first action handler should be executed. This will allow to write handler for specific resource type, and have a fallback for general types.

Test initial repository scanner

1. Create SQS repository
2. On registration, send message into the queue

Should work similar to testSQS but with repository

Set more env variables

RESOURCE_ANCESTOR_NAME, type, HANDLER_NAME/type, KEYS location

Create EC2 Instance handler

Create initial repository scanner

Should discover all resources/handlers, register them and trigger all events - all during startup