JSON is a subset of YAML, so anything you see in YAML can be done in
JSON, .. the real question is SHOULD YOU?
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails
Just for curiosity, why are you using json instead of yaml?
On Wed, Jun 26, 2019 at 11:33 PM Narahari 'n' Savitha
wrote:
> James pointed out the mistakes in the json and now it works.
> I am able to use json as valid format for playboks.
>
> On Wednesday, June 26, 2019 at 7:18:22 PM UTC-4,
James pointed out the mistakes in the json and now it works.
I am able to use json as valid format for playboks.
On Wednesday, June 26, 2019 at 7:18:22 PM UTC-4, Michael M wrote:
>
> Playbooks must be in yaml. Inventories can be in json (at least dynamic
> inventories require it), but not the
On Wed, Jun 26, 2019, at 6:08 PM, Narahari 'n' Savitha wrote:
> Hello Folkds:
>
> Thank you in advance for your time and attention.
>
> I wrote a playbook in the json format.
>
> > [
> > {
> > "name": "Test the json mode"
Missing a comma.
> > "hosts": "cool_columbus",
> > "tasks": [
> >
Playbooks must be in yaml. Inventories can be in json (at least dynamic
inventories require it), but not the playbooks themselves.
On 6/26/19 3:08 PM, Narahari 'n' Savitha wrote:
Hello Folkds:
Thank you in advance for your time and attention.
I wrote a playbook in the json format.
[
Hello Folkds:
Thank you in advance for your time and attention.
I wrote a playbook in the json format.
[
> {
> "name": "Test the json mode"
> "hosts": "cool_columbus",
> "tasks": [
> {
> "name": "First task"
> "shell": {
> "chdir": "/tmp",
>
