admin/skato-ansible
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

Rewrite all access of attributes/methods not native to Ansible modules to use bracket notation #5

New Issue
Open
opened 2025-12-16 17:04:24 +00:00 by admin · 0 comments
admin commented 2025-12-16 17:04:24 +00:00
Owner
Copy Link

The Ansible YAML code should eventually be rewritten to abide by the following two rules for variable reference/use, before the project balloons too much in size:

  • Accessed attributes/methods that are not native to an Ansible module, or are from an object not native to Ansible or its modules, should use bracket notation for that access.
  • Accessed attributes/methods that are native to an Ansible module, or are from an object native to Ansible or its modules, should use dot notation for that access, unless the intention is to use a variable to specify the name of the attribute or method being accessed.

Following these rules make namespace conflicts less likely, and therefore reduces the likelihood of bugs.

The Ansible YAML code should eventually be rewritten to abide by the following two rules for variable reference/use, before the project balloons too much in size: - Accessed attributes/methods that are not native to an Ansible module, or are from an object not native to Ansible or its modules, should use **bracket notation** for that access. - Accessed attributes/methods that *are* native to an Ansible module, or are from an object native to Ansible or its modules, should use **dot notation** for that access, *unless the intention is to use a variable to specify the name of the attribute or method being accessed*. Following these rules make namespace conflicts less likely, and therefore reduces the likelihood of bugs.
admin added the qol/refactor label 2025-12-16 17:04:24 +00:00
admin self-assigned this 2025-12-16 17:04:24 +00:00
admin added this to the skato-ansible debugging project 2025-12-16 17:06:55 +00:00
admin moved this to Low Priority in skato-ansible debugging on 2025-12-16 17:07:20 +00:00
admin moved this to Needs Triage in skato-ansible debugging on 2025-12-16 17:07:49 +00:00
Sign in to join this conversation.
main
Branches Tags
Labels
Clear labels
dox
expand
1
The documentation needs to explain or cover an additional feature or procedure.
dox
redact
The documentation contains outdated information that should be removed, or incorrect information that should be corrected.
fix/boundary_bug
Fix a bug that arose from unintended or inapproriate usage
 fix/compatibility_bug
Fix semantic errors arising from differences in execution environment
 fix/performance_bug
Fix low throughput, high response times or high load times.
 fix/semantic_error
Fix an unintended, albeit working, behavior or function, i.e. a functional or logical bug
 fix/syntactic_error
Fix a bug caused by a syntactic error, or anticipate deprecated programming language BIFs, reserved keywords or delimiters
 fix/usability_bug
Reduce friction in the acheivement of certain end-uses within the scope or broad use case of the project
 fix/workflow_bug
Fix an error resulting from structural flaws in the decision tree or I/O flowchart of related procedures
 qol/feature
A proposal for an additional or useful feature that increases quality of life.
 qol/refactor
Refactor of code that adds quality of life by either reducing technical debt or further easing user customization or future feature extensions.
No Label qol/refactor
Milestone
No items
No Milestone
Projects
Clear projects
No project skato-ansible debugging
Assignees
Clear assignees
admin
No Assignees admin
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/skato-ansible#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?