This repo has been shrunk down and moved to https://github.com/mozilla-services/sign-xpi/. What remains is left here for historical purposes only.
This project uses AWS Step Function state machines to manage the workflow for shipping system addons. This project is EXPERIMENTAL. The goal is to learn and determine if AWS Step Functions are appropriate for managing addon work flows.
The first milestone a prototype that ships systems addons. This is a good place to start the current process is not automated and fairly well defined.
We're hacking out a prototype. Speed is most important but we also want some process. For now, file an PR with code or closing an issue, get it reviewed and squash merge it into master.
We may create a more formal contribution process if/when we are sure step functions are the right approach.
Also:
- Use GH issues to track discussion and make decisions.
- Issues should added to the appropriate milestones
- Discuss issues on irc.mozilla.org in the #storage channel.
/
apex/ - lambda functions managed by apex
functions/
apps/ - custom apps (manual input steps, etc)
signoff/
state_machines/ - top level dir for Step Functions
system_addons/ - system addon step function resources
Deploying AWS Lambda Functions:
- Merge everything into
master
- CI (CircleCI) will use Apex to deploy it to the AWS Dev Account
Deploying Step Functions:
- ... ?
Resources for AWS Step Functions:
Resources for AWS Lambda:
- Apex - tool for managing lambda deployments
- Programming Model
- Creating a deployment package
- Versioning
- API Reference