ansible #50
Merged
ansible #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
December 12, 2019 14:20
inital work posting to github. looking to work with the community and veritas on the ansible deployments. msdp_create and vmware_resourcelimits need some assitance. although it looks right from the swagger docs, it seems to through an api error.
updated body yaml to correct syntax.
Updated to one call
kenogden
previously approved these changes
May 29, 2020
vmware asset groups post for vmware filter based on folders.
an example of how we are doing a slo post.
slo_post example
new file added for vmware asset-groups
|
Added two more files. |
rkennedy
approved these changes
Jul 30, 2020
| @@ -0,0 +1,25 @@ | |||
| ### NetBackup API Code Samples for Ansible | |||
There was a problem hiding this comment.
Let's start headings at level 1 instead of level 3, please.
Suggested change
| ### NetBackup API Code Samples for Ansible | |
| # NetBackup API Code Samples for Ansible |
| #### Pre-requisites: | ||
|
|
||
| - NetBackup 8.1.1 or higher | ||
| - ansible 2.x |
There was a problem hiding this comment.
Capitalize proper nouns.
Suggested change
| - ansible 2.x | |
| - Ansible 2.x |
Comment on lines
+19
to
+21
| tasks: | ||
| -name: name of tasks | ||
| include_task: tasklocation/taskname |
There was a problem hiding this comment.
Mark for display as code, and make it valid YAML syntax.
Suggested change
| tasks: | |
| -name: name of tasks | |
| include_task: tasklocation/taskname | |
| ```yaml | |
| tasks: | |
| - name: name of tasks | |
| include_task: tasklocation/taskname | |
| \``` |
Comment on lines
+15
to
+19
| register: login | ||
|
|
||
| - name: set facts | ||
| set_fact: | ||
| login_token: "{{login.json.token}}" |
There was a problem hiding this comment.
Some plays use login_token, and others use login.json.token directly. What's the difference?
Comment on lines
+24
to
+25
| Vars for ansible are defined in a inventory file for use in plays | ||
| vars created during plays are used in future ones like login.yml. |
There was a problem hiding this comment.
Markdown renders this as one sentence. And passive voice makes it unclear whose responsibility it is to perform the actions described here.
Suggested change
| Vars for ansible are defined in a inventory file for use in plays | |
| vars created during plays are used in future ones like login.yml. | |
| Define variables for Ansible in an inventory file for use in plays. | |
| Variables registered during plays like login.yaml are used in subsequent plays. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The start of an ansible snipit section with some tested code against 8.2