Help wanted! We'd love your contributions to Mutato. Please review the following guidelines before contributing. Also, feel free to propose changes to these guidelines by updating this file and submitting a pull request.
Please don't open a GitHub issue for questions about how to use mutato, as the goal is to use issues for managing bugs and feature requests. Issues that are related to general support will be closed and redirected to our gitter room.
For all support related questions, please ask the question in our gitter room: stelligent/mutato.
If you've identified a bug in mutato, please submit an issue to our GitHub repo: stelligent/mutato. Please also feel free to submit a Pull Request with a fix for the bug!
All feature requests should start with submitting an issue documenting the user story and acceptance criteria. Again, feel free to submit a Pull Request with a proposed implementation of the feature.
Before submitting a new issue, please search the issues to make sure there isn't a similar issue doesn't already exist.
Assuming no existing issues exist, please ensure you include the following bits of information when submitting the issue to ensure we can quickly reproduce your issue:
- Version of mutato
- Platform (Linux, OS X, Windows)
- The complete
mutato.ymlfile used - The complete command that was executed
- Any output from the command
- Details of the expected results and how they differed from the actual results
We may have additional questions and will communicate through the GitHub issue, so please respond back to our questions to help reproduce and resolve the issue as quickly as possible.
New issues can be created with in our GitHub repo.
Pull requests should target the develop branch. Ensure you have a successful
build for your branch. Please also reference the issue from the description of
the pull request using special keyword
syntax to
auto close the issue when the PR is merged. For example, include the phrase
fixes #14 in the PR description to have issue #14 auto close.
When submitting code, please make every effort to follow existing conventions and style in order to keep the code as readable as possible. Here are a few points to keep in mind:
- Please run
npm run-script lint:checkbefore committing to ensure code aligns with go standards. - Ensure all Classes, and Functions are documented appropriately as for the
JSDoc standard. See the project
README.mdfor these instructions. - All dependencies must be defined in the
package.jsonfile and pinned to a patch range. This is accomplished via a command likenpm install --save-dev {PKG}for development dependencies ornpm install {PKG}otherwise
Also, consider the original design principles:
- Polyglot - There will be no prescribed language or framework for developing the microservices. The only requirement will be that the service will be run inside a container and exposed via an HTTP endpoint.
- Cloud Provider - At this point, the tool will assume AWS for the cloud provider and will not be written in a cloud agnostic manner. However, this does not preclude refactoring to add support for other providers at a later time.
- Declarative - All resource administration will be handled in a declarative vs. imperative manner. A file will be used to declared the desired state of the resources and the tool will simply assert the actual state matches the desired state. The tool will accomplish this by generating CloudFormation templates.
- Stateless - The tool will not maintain its own state. Rather, it will rely on the CloudFormation stacks to determine the state of the platform.
- Secure - All security will be managed by AWS IAM credentials. No additional authentication or authorization mechanisms will be introduced.
By contributing your code, you agree to license your contribution under the terms of the MIT License.
All files are released with the MIT license.