Merge pull request #542 from jladdjr/awx_349_acceptance_doc

Update custom credential document for mult-file injection
This commit is contained in:
Jim Ladd
2017-10-31 19:14:37 -04:00
committed by GitHub

View File

@@ -181,6 +181,20 @@ certificate/key data:
} }
} }
3.3 adds the ability for a single ``Credential Type`` to inject multiple files:
"injectors": {
"file": {
"template.cert": "{{cert}}",
"template.key": "{{key}}"
},
"env": {
"MY_CERT": "{{tower.filename.cert}",
"MY_KEY": "{{tower.filename.key}}"
}
}
Job and Job Template Credential Assignment Job and Job Template Credential Assignment
------------------------------------------ ------------------------------------------
@@ -309,6 +323,9 @@ When verifying acceptance we should ensure the following statements are true:
* Superusers (and only superusers) should be able to define custom `Credential * Superusers (and only superusers) should be able to define custom `Credential
Types`. They should properly inject environment variables, extra vars, and Types`. They should properly inject environment variables, extra vars, and
files for playbook runs, SCM updates, inventory updates, and ad-hoc runs. files for playbook runs, SCM updates, inventory updates, and ad-hoc runs.
* Custom `Credential Types` should support injecting both single and
multiple files. (Furthermore, the new syntax for injecting multiple files
should work properly even if only a single file is injected).
* The default `Credential Types` included with Tower in 3.2 should be * The default `Credential Types` included with Tower in 3.2 should be
non-editable/readonly and cannot be deleted by any user. non-editable/readonly and cannot be deleted by any user.
* Stored `Credential` values for _all_ types should be consistent before and * Stored `Credential` values for _all_ types should be consistent before and