bootstrap-vz/bootstrapvz/plugins/ansible/manifest-schema.yml

---
$schema: http://json-schema.org/draft-04/schema#
title: Ansible plugin manifest
type: object
properties:
  plugins:
    type: object
    properties:
      ansible:
        type: object
        properties:
          extra_vars: {type: string}
          tags: {type: string}
          skip_tags: {type: string}
          opt_flags:
            type: array
            flag: {type: string}
            minItems: 1
          hosts:
            type: array
            host: {type: string}
            minItems: 1
          playbook:
            type: string
            pattern: ^[^\0]+$
        required: [playbook]
        additionalProperties: false
Added an Ansible plugin, which runs a playbook on the chroot before before build completion. NOTE: I'm not doing any validation on the opt_flags param and I don't recommend using for more then adding a -vvvv. Also, I'm purposely excluding the vault flags (which also pretty commonly used) because you shouldn't be baking private keys and certs into your images. Instead, just avoid running the vault specific code or use the opt_flags if absolutely necessary. 2014-12-22 23:01:35 -06:00			`---`
			`$schema: http://json-schema.org/draft-04/schema#`
			`title: Ansible plugin manifest`
			`type: object`
			`properties:`
			`plugins:`
			`type: object`
			`properties:`
			`ansible:`
			`type: object`
			`properties:`
			`extra_vars: {type: string}`
			`tags: {type: string}`
			`skip_tags: {type: string}`
			`opt_flags:`
			`type: array`
			`flag: {type: string}`
			`minItems: 1`
			`hosts:`
			`type: array`
			`host: {type: string}`
			`minItems: 1`
ansible: Make playbook path relative to manifest 2017-07-14 18:26:25 +02:00			`playbook:`
			`type: string`
			`pattern: ^[^\0]+$`
Litter the manifest schemas with additionalProperties:false This pretty much eliminates the possiblity of undiscovered typos in the manifest 2015-05-02 12:45:55 +02:00			`required: [playbook]`
			`additionalProperties: false`