Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

60%
+1 −0
Q&A How to validate Ansible role dictionary argument's "additionalProperties"

In JSON Schema one can use the additionalProperties key to validate properties whose names are not know. You can still impose restrictions on their type. How to do this in an Ansible role argument...

1 answer  ·  posted 1y ago by Iizuki‭  ·  edited 1y ago by Iizuki‭

Question ansible
#3: Post edited by user avatar Iizuki‭ · 2023-10-11T13:43:58Z (about 1 year ago)
Grammar
  • How to validate Ansible role dictionary arguments "additionalProperties"
  • How to validate Ansible role dictionary argument's "additionalProperties"
#2: Post edited by user avatar Iizuki‭ · 2023-10-11T13:10:56Z (about 1 year ago)
Removed clutter
  • In JSON Schema one can use the [additionalProperties](https://json-schema.org/understanding-json-schema/reference/object#additional-properties) key to validate properties whose names are not know. You can still impose restrictions on their type.
  • **How to do this in an [Ansible role argument spec](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#role-argument-validation)?**
  • This doesn't work:
  • ```yaml
  • argument_specs:
  • main:
  • short_description: The main entry point for the myapp role.
  • options:
  • dictionary_argument:
  • description: A map from string to integers.
  • type: dict
  • required: true
  • options:
  • type: int
  • ```
  • In JSON Schema one can use the [additionalProperties](https://json-schema.org/understanding-json-schema/reference/object#additional-properties) key to validate properties whose names are not know. You can still impose restrictions on their type.
  • **How to do this in an [Ansible role argument spec](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#role-argument-validation)?**
  • This doesn't work:
  • ```yaml
  • argument_specs:
  • main:
  • options:
  • dictionary_argument:
  • description: A map from string to integers.
  • type: dict
  • required: true
  • options:
  • type: int
  • ```
#1: Initial revision by user avatar Iizuki‭ · 2023-10-11T13:08:16Z (about 1 year ago)
How to validate Ansible role dictionary arguments "additionalProperties"
In JSON Schema one can use the [additionalProperties](https://json-schema.org/understanding-json-schema/reference/object#additional-properties) key to validate properties whose names are not know. You can still impose restrictions on their type.

**How to do this in an [Ansible role argument spec](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#role-argument-validation)?**

This doesn't work:
```yaml
argument_specs:
  main:
    short_description: The main entry point for the myapp role.
    options:
      dictionary_argument:
        description: A map from string to integers.
        type: dict
        required: true
        options:
          type: int
```