You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Maykel Moya 811aa2611e Add support for string values
The SET GLOBAL statement requires properly quoting of values. For example, the
following correct queries will fail if quotes are toggled:

mysql> SET GLOBAL innodb_lru_scan_depth = 2000;
mysql> SET GLOBAL master_info_repository = "TABLE";

`mysql_variable` module doesn't quote the value argument, therefore
string values will fail.

  # this task will pass, 2000 is passed without quotes
  - name: set a numeric value
    mysql_variable: variable=innodb_lru_scan_depth value=2000

  # this task will fail, TABLE is passed without quotes
  - name: set a string value
    mysql_variable: variable=master_info_repository value=TABLE

With this patch prepared statements are used. Proper quoting will be
done automatically based on the type of the variables thus an attempt
to convert to int, then to float is done in first place.

Booleans values, ie: ON, OFF, are not specially handled because they
can be quoted. For example, the following queries are correct and
equivalent, they all set _innodb_file_per_table_ to logical _True_:

mysql> SET GLOBAL innodb_file_per_table = "ON";
mysql> SET GLOBAL innodb_file_per_table = ON;
mysql> SET GLOBAL innodb_file_per_table = 1;

Tested in mysql 5.5 and 5.6.
11 years ago
bin More site rename things. 11 years ago
docs/man Add reference to Guru to sidebar. 11 years ago
docsite Add some notes on installing on FreeBSD 11 years ago
examples Fix various typos in markdown documentation 11 years ago
hacking Allow hacking/env-setup module path to use config file library path 11 years ago
lib/ansible When using jsonify in modules, try several unicode encoding for dumps() 11 years ago
library Add support for string values 11 years ago
packaging Fix various typos in markdown documentation 11 years ago
plugins Save api id to index as an int instead of a list 11 years ago
test Fixing tests for git 11 years ago
.gitignore Further modifications to the module formatter to adjust to the new theme, and some misc docs text corrections. 11 years ago
CHANGELOG.md Update changelog for ec2 exact_count and count_tag 11 years ago
CODING_GUIDELINES.md Fix various typos in markdown documentation 11 years ago
CONTRIBUTING.md Update bug reporting instructions to refer to the issue template 11 years ago
COPYING license file should be in source tree 13 years ago
MANIFEST.in Add some docs/examples 12 years ago
Makefile Remove man3 stuff since this is available via ansible-doc, rpm target should 11 years ago
README.md AnsibleWorks -> Ansible 11 years ago
RELEASES.txt Update RELEASES.txt 11 years ago
VERSION Version bump for 1.5 11 years ago
setup.py AnsibleWorks -> Ansible 11 years ago

README.md

PyPI version

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read the documentation and more at http://ansible.com/

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions here for a variety of platforms. If you want a tarball of the last release, go to releases.ansible.com and you can also install with pip.

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

  • Read Contributing.md for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
  • When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
  • All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
  • irc.freenode.net: #ansible

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases
  • We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansible.com

Ansible, Inc