-'A dictionary array of subnets to add of the form: { cidr: ..., az: ... , resource_tags: ... }. Where az is the desired availability zone of the subnet, but it is not required. Tags (i.e.: resource_tags) is also optional and use dictionary form: {"Environment":"Dev", "Tier":"Web", ...}. All VPC subnets not in this list will be removed. As of 1.8, if the subnets parameter is not specified, no existing subnets will be modified.'
required:false
default:null
aliases:[]
vpc_id:
description:
-AVPCidtoterminatewhenstate=absent
required:false
default:null
aliases:[]
resource_tags:
description:
-'A dictionary array of resource tags of the form: { tag1: value1, tag2: value2 }. Tags in this list are used in conjunction with CIDR block to uniquely identify a VPC in lieu of vpc_id. Therefore, if CIDR/Tag combination does not exist, a new VPC will be created. VPC tags not on this list will be ignored. Prior to 1.7, specifying a resource tag was optional.'
required:true
default:null
aliases:[]
version_added:"1.6"
internet_gateway:
description:
@ -69,31 +65,26 @@ options:
required:false
default:"no"
choices:["yes","no"]
aliases:[]
route_tables:
description:
-'A dictionary array of route tables to add of the form: { subnets: [172.22.2.0/24, 172.22.3.0/24,], routes: [{ dest: 0.0.0.0/0, gw: igw},], resource_tags: ... }. Where the subnets list is those subnets the route table should be associated with, and the routes list is a list of routes to be in the table. The special keyword for the gw of igw specifies that you should the route should go through the internet gateway attached to the VPC. gw also accepts instance-ids in addition igw. resource_tags is optional and uses dictionary form: {"Name": "public", ... }. This module is currently unable to affect the "main" route table due to some limitations in boto, so you must explicitly define the associated subnets or they will be attached to the main table implicitly. As of 1.8, if the route_tables parameter is not specified, no existing routes will be modified.'
-'A dictionary array of route tables to add of the form: { subnets: [172.22.2.0/24, 172.22.3.0/24,], routes: [{ dest: 0.0.0.0/0, gw: igw},], resource_tags: ... }. Where the subnets list is those subnets the route table should be associated with, and the routes list is a list of routes to be in the table. The special keyword for the gw of igw specifies that you should the route should go through the internet gateway attached to the VPC. gw also accepts instance-ids, interface-ids, and vpc-peering-connection-ids in addition igw. resource_tags is optional and uses dictionary form: {"Name": "public", ... }. This module is currently unable to affect the "main" route table due to some limitations in boto, so you must explicitly define the associated subnets or they will be attached to the main table implicitly. As of 1.8, if the route_tables parameter is not specified, no existing routes will be modified.'
module.fail_json(msg="unable to connect to database, check login_user and login_password are correct or %s has the credentials. Exception message: %s"%(config_file,e))
else:
module.fail_json(msg="unable to connect, check login credentials (login_user, and login_password, which can be defined in ~/.my.cnf), check that mysql socket exists and mysql server is running (ERROR: %s%s)"%(errno,errstr))
module.fail_json(msg="unable to find %s. Exception message: %s"%(config_file,e))
# Create database user with name 'bob' and previously hashed mysql native password '*EE0D72C1085C46C5278932678FBE2C6A782821B4' with all database privileges
module.fail_json(msg="unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: %s"%e)
module.fail_json(msg="unable to connect to database, check login_user and login_password are correct or %s has the credentials. Exception message: %s"%(config_file,e))
module.fail_json(msg="unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials")
ifos.path.exists(config_file):
module.fail_json(msg="unable to connect to database, check login_user and login_password are correct or %s has the credentials. Exception message: %s"%(config_file,e))
else:
module.fail_json(msg="unable to find %s. Exception message: %s"%(config_file,e))
mysqlvar_val=getvariable(cursor,mysqlvar)
ifmysqlvar_valisNone:
module.fail_json(msg="Variable not available \"%s\""%mysqlvar,changed=False)
-Apackagename,likeC(foo),orpackagespecifierwithversion,likeC(foo=1.0).Namewildcards(fnmatch)likeC(apt*)andversionwildcardslikeC(foo=1.0*)arealsosupported.Notethattheapt-getcommandlinesupportsimplicitregexmatchesherebutwedonotbecauseitcanlettyposthrougheasier(IfyoutypoC(foo)asC(fo)apt-getwouldinstallpackagesthathave"fo"intheirnamewithawarningandapromptfortheuser.Sincewedon't have warnings and prompts before installing we disallow this. Use an explicit fnmatch pattern if you want wildcarding)
-CorrespondstotheC(--no-install-recommends)optionforI(apt).Default behavior(C(yes))replicatesapt's default behavior; C(no) does not install recommended packages. Suggested packages are never installed.
# along with Ansible. If not, see <http://www.gnu.org/licenses/>.
#
importtraceback
importos
importyum
importrpm
@ -51,7 +49,7 @@ options:
-"Package name, or package specifier with version, like C(name-1.0). When using state=latest, this can be '*' which means run: yum -y update. You can also pass a url or a local path to a rpm file. To operate on several packages this can accept a comma separated list of packages or (as of 2.0) a list of packages."
required:true
default:null
aliases:[]
aliases:['pkg']
exclude:
description:
-"Package name(s) to exclude when state=present, or latest"
results['msg']='%s%s'%(results.get('msg',''),'Warning: Due to potential bad behaviour with rhnplugin and certificates, used slower repoquery calls instead of Yum API.')
results['msg']='%s%s'%(results.get('msg',''),
'Warning: Due to potential bad behaviour with rhnplugin and certificates, used slower repoquery calls instead of Yum API.')
Bermudez, Jaime
9 years ago