@@ -65,7 +65,7 @@ INSTALL.rst molecule.yml converge.yml verify.yml
65
65
role. Molecule will invoke this playbook with ` ansible-playbook ` and
66
66
run it against an instance created by the driver.
67
67
- ` verify.yml ` is the Ansible file used for testing as Ansible is the
68
- default [ verifier] ( / configuration/ #verifier) . This allows you to
68
+ default [ verifier] ( configuration.md #verifier ) . This allows you to
69
69
write specific tests against the state of the container after your
70
70
role has finished executing. Other verifier tools are available
71
71
Note that [ testinfra] ( https://testinfra.readthedocs.io/en/latest/ ) was the default verifier prior to molecule version 3.
@@ -98,24 +98,24 @@ The `molecule.yml` is for configuring Molecule. It is a
98
98
[ YAML] ( https://yaml.org/ ) file whose keys represent the high level
99
99
components that Molecule provides. These are:
100
100
101
- - The [ dependency] ( / configuration/ #dependency) manager. Molecule
101
+ - The [ dependency] ( configuration.md #dependency ) manager. Molecule
102
102
uses [ galaxy development guide]
103
103
by default to resolve your role dependencies.
104
- - The [ driver] ( / configuration/ #driver) provider. Molecule uses
104
+ - The [ driver] ( configuration.md #driver ) provider. Molecule uses
105
105
[ Docker] ( https://docs.docker.com/ ) by default. Molecule uses the
106
106
driver to delegate the task of creating instances.
107
- - The [ platforms] ( / configuration/ #platforms) definitions. Molecule
107
+ - The [ platforms] ( configuration.md #platforms ) definitions. Molecule
108
108
relies on this to know which instances to create, name and to which
109
109
group each instance belongs. If you need to test your role against
110
110
multiple popular distributions (CentOS, Fedora, Debian), you can
111
111
specify that in this section.
112
- - The [ provisioner] ( / configuration/ #provisioner) . Molecule only
112
+ - The [ provisioner] ( configuration.md #provisioner ) . Molecule only
113
113
provides an Ansible provisioner. Ansible manages the life cycle of
114
114
the instance based on this configuration.
115
115
- The [ scenario] [ ] definition.
116
116
Molecule relies on this configuration to control the scenario
117
117
sequence order.
118
- - The [ verifier] ( / configuration/ #verifier) framework. Molecule
118
+ - The [ verifier] ( configuration.md #verifier ) framework. Molecule
119
119
uses Ansible by default to provide a way to write specific state
120
120
checking tests (such as deployment smoke tests) on the target
121
121
instance.
0 commit comments