question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItΒ collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doc bug - Getting Started Guide - Scenario Layout does not match described example

See original GitHub issue

Issue Type

  • Bug report for documentation

Molecule and Ansible details

$ ansible --version && molecule --version
ansible 2.9.5
  config file = None
  configured module search path = ['/home/max/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/max/.local/lib/python3.6/site-packages/ansible
  executable location = /home/max/.local/bin/ansible
  python version = 3.6.9 (default, Nov  7 2019, 10:44:02) [GCC 8.3.0]
molecule 3.0.2
   ansible==2.9.5 python==3.6

Molecule installation method (one of):

  • pip

Ansible installation method (one of):

  • pip

Desired Behavior

The described layout in section The Scenario Layout matches the one created by the example.

Actual Behaviour

The directory molecule/default does not contain the file Dockerfile.j2, nor the directory tests (which exists in the root director).

$ molecule init role my-new-role
--> Initializing new role my-new-role...
$ tree
.
└── my-new-role
    β”œβ”€β”€ defaults
    β”‚Β Β  └── main.yml
    β”œβ”€β”€ files
    β”œβ”€β”€ handlers
    β”‚Β Β  └── main.yml
    β”œβ”€β”€ meta
    β”‚Β Β  └── main.yml
    β”œβ”€β”€ molecule
    β”‚Β Β  └── default
    β”‚Β Β      β”œβ”€β”€ converge.yml
    β”‚Β Β      β”œβ”€β”€ INSTALL.rst
    β”‚Β Β      β”œβ”€β”€ molecule.yml
    β”‚Β Β      └── verify.yml
    β”œβ”€β”€ README.md
    β”œβ”€β”€ tasks
    β”‚Β Β  └── main.yml
    β”œβ”€β”€ templates
    β”œβ”€β”€ tests
    β”‚Β Β  β”œβ”€β”€ inventory
    β”‚Β Β  └── test.yml
    └── vars
        └── main.yml

11 directories, 12 files

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:11 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
ssbarneacommented, Mar 12, 2020

I think that the section is explained good enough, probably you did not use the latest branch when reading the documentation. Still, feel free to propose a PR that improves it.

1reaction
PhilippSeleniumcommented, Dec 29, 2021

Current link to Dockerfile.j2

Since this is still an issue I would also opt to reopen it

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to write a bug report effectively: examples and templates
Learn how to write bug reports effectively with this guide, including examples and templates. We've also included downloadable templates inΒ ...
Read more >
Auto Layout Guide: Working with Constraints in Interface Builder
In iOS, the system provides the size and layout of the scene. Auto Layout can modify only the contents of the scene.
Read more >
Documentation Style Guide - GitLab Docs
Documentation Style Guide. This document defines the standards for GitLab documentation, including grammar, formatting, word use, and more.
Read more >
Testing your Compose layout - Jetpack - Android Developers
In Compose, only some composables emit UI into the UI hierarchy, therefore a different approach to matching UI elements is needed. Semantics. UI...
Read more >
Troubleshooting - Unity - Manual
Problems installing git dependencies, - No 'git' executable was found ... You can also run the Unity Package Manager Diagnostics tool if you...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found