Ansible dictionary key as variable

up vote
1
down vote

favorite

Let's have something like this in role defaults/main.yml:

num: 0

config:

  0:

    a: true

    b: 'x'

  1:

    a: false

    b: 'y'

  2:

    a: false

    b: 'z'

Now I send -e num=1 in playbook call, and I want to use values a and b based on this value somewhere else in the role, something like:

aValue: '{{config[num].a}}'

bValue: '{{config[num].b}}'

How do I do that? I tried

aValue: '{{config[num].a}}'
but got an error: 'dict object' has no attribute u'1'

aValue: '{{config["num"].a}}'
but got an error: 'dict object' has no attribute 'num'

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

add a comment |

up vote
1
down vote

favorite

Let's have something like this in role defaults/main.yml:

num: 0

config:

  0:

    a: true

    b: 'x'

  1:

    a: false

    b: 'y'

  2:

    a: false

    b: 'z'

Now I send -e num=1 in playbook call, and I want to use values a and b based on this value somewhere else in the role, something like:

aValue: '{{config[num].a}}'

bValue: '{{config[num].b}}'

How do I do that? I tried

aValue: '{{config[num].a}}'
but got an error: 'dict object' has no attribute u'1'

aValue: '{{config["num"].a}}'
but got an error: 'dict object' has no attribute 'num'

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

add a comment |

up vote
1
down vote

favorite

Let's have something like this in role defaults/main.yml:

num: 0

config:

  0:

    a: true

    b: 'x'

  1:

    a: false

    b: 'y'

  2:

    a: false

    b: 'z'

Now I send -e num=1 in playbook call, and I want to use values a and b based on this value somewhere else in the role, something like:

aValue: '{{config[num].a}}'

bValue: '{{config[num].b}}'

How do I do that? I tried

aValue: '{{config[num].a}}'
but got an error: 'dict object' has no attribute u'1'

aValue: '{{config["num"].a}}'
but got an error: 'dict object' has no attribute 'num'

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

Let's have something like this in role defaults/main.yml:

num: 0

config:

  0:

    a: true

    b: 'x'

  1:

    a: false

    b: 'y'

  2:

    a: false

    b: 'z'

Now I send -e num=1 in playbook call, and I want to use values a and b based on this value somewhere else in the role, something like:

aValue: '{{config[num].a}}'

bValue: '{{config[num].b}}'

How do I do that? I tried

aValue: '{{config[num].a}}'
but got an error: 'dict object' has no attribute u'1'

aValue: '{{config["num"].a}}'
but got an error: 'dict object' has no attribute 'num'

automation continuous-integration ansible jinja2

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

edited Nov 14 at 7:53

asked Nov 14 at 6:38

lubik

asked Nov 14 at 6:38

lubik

asked Nov 14 at 6:38

lubik

add a comment |

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

If you quote those config keys, they will become strings:

config:

  "0":

     a: true

Or, if you have the rest of your playbook that really does want them to be numbers, you can make num actually be a number in two ways:

ansible -e '{"num": 1}' to cause ansible to parse --extra-vars as JSON, where "num" really will be a Number (in the JSON sense)

or coerce num in the jinja2 expression:

aValue: '{{ config[ (num|int) ].a }}'

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53294414%2fansible-dictionary-key-as-variable%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

If you quote those config keys, they will become strings:

config:

  "0":

     a: true

Or, if you have the rest of your playbook that really does want them to be numbers, you can make num actually be a number in two ways:

ansible -e '{"num": 1}' to cause ansible to parse --extra-vars as JSON, where "num" really will be a Number (in the JSON sense)

or coerce num in the jinja2 expression:

aValue: '{{ config[ (num|int) ].a }}'

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

add a comment |

up vote
2
down vote

accepted

If you quote those config keys, they will become strings:

config:

  "0":

     a: true

Or, if you have the rest of your playbook that really does want them to be numbers, you can make num actually be a number in two ways:

ansible -e '{"num": 1}' to cause ansible to parse --extra-vars as JSON, where "num" really will be a Number (in the JSON sense)

or coerce num in the jinja2 expression:

aValue: '{{ config[ (num|int) ].a }}'

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

add a comment |

up vote
2
down vote

accepted

If you quote those config keys, they will become strings:

config:

  "0":

     a: true

Or, if you have the rest of your playbook that really does want them to be numbers, you can make num actually be a number in two ways:

ansible -e '{"num": 1}' to cause ansible to parse --extra-vars as JSON, where "num" really will be a Number (in the JSON sense)

or coerce num in the jinja2 expression:

aValue: '{{ config[ (num|int) ].a }}'

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

If you quote those config keys, they will become strings:

config:

  "0":

     a: true

Or, if you have the rest of your playbook that really does want them to be numbers, you can make num actually be a number in two ways:

ansible -e '{"num": 1}' to cause ansible to parse --extra-vars as JSON, where "num" really will be a Number (in the JSON sense)

or coerce num in the jinja2 expression:

aValue: '{{ config[ (num|int) ].a }}'

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

answered Nov 14 at 7:59

Matthew L Daniel

6,82112326

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrgtkky