salt-cloud is Now Part of Salt!
This repository is deprecated.
All new pull requests and issues should be filed against the main Salt repository.
The Salt team is excited to report that the
salt-cloud repository has been
merged into the main Salt repository.
The merge happened on November 8th, 2013 in pull request #8352.
Frequently asked questions
- What Salt release includes
- Salt will include native
salt-cloudin the Salt Hydrogen release.
- What does this mean for the future of
One fewer dependency.
salt-cloudwill continue to operate in the same way and the config files will live in the same location as before. The only end-user difference is
salt-cloudwill not need to be installed as a separate package.
- What will happen to the
salt-cloudrepository and issue tracker?
- We will leave the
salt-cloudrepository in place on GitHub for the foreseeable future. It will contain this deprecation notice and serve as a historical reference.
- Has the commit history and authorship for
We have merged these two repositories using
git mvfollowed by a regular
git mergethat preserves all the rich Git history and authorship of
salt-cloud. All commits made to
salt-cloudcan be referenced using the exact same SHA1 in the Salt repository.
In order to view the full history of a file that came from the
salt-cloudrepository from within the Salt repository use the
--followflag in Git. Unfortunately, at the time of writing, GitHub's history view does not include this flag. For example, to view the full history of the
git log --follow path/to/clouds/ec2.py
Note, any commit messages that reference GitHub issues from a commit from
salt-cloudwill get confused and link to the corresponding issue in the Salt repository (if there is one of that same issue number).