Skip to content

teragrep/cfp_01

Repository files navigation

CFP_01: Easy to use CFEngine containers

Provides easy to use, systemd-based containers with CFEngine already installed. Intended to be used with containerized tests that requires CFEngine.

Features

Easy to run and extend.

Custom entrypoint logic can be inserted and automatically executed without having to worry about creating systemd service files.

Builds both plain systemd and systemd-ipa containers.

Supported plain systemd containers:

Container name Based on

ghcr.io/teragrep/cfp_01/systemd/el8:latest

rockylinux/rockylinux:8

ghcr.io/teragrep/cfp_01/systemd/el9:latest

rockylinux/rockylinux:9

Supported systemd-ipa containers that extends ipa_01:

Container name Based on

ghcr.io/teragrep/cfp_01/systemd-ipa/el8:latest

ghcr.io/teragrep/ipa_01/client/el8:1.0.0

ghcr.io/teragrep/cfp_01/systemd-ipa/el9:latest

ghcr.io/teragrep/ipa_01/client/el9:1.0.0

The containers can be pinned to certain releases instead of :latest, for example with :1.0.0. Full list of versions can be found in packages list.

Documentation

See the official documentation on docs.teragrep.com.

Limitations

All bootstrapping and promise execution logic must be provided by the user.

How to use

See tests/functionality for example use.

You can provide /cfp_01.entrypoint.sh for the service cfp_01 to execute on startup if any custom bootstrapping logic is wanted.

The systemd-ipa containers requires some setup and ipa_01 service to be fully finished before service cfp_01 is executed.

Contributing

You can involve yourself with our project by opening an issue or submitting a pull request.

Contribution requirements:

  1. All changes must be accompanied by a new or changed test. If you think testing is not required in your pull request, include a sufficient explanation as why you think so.

  2. Security checks must pass

  3. Pull requests must align with the principles and values of extreme programming.

  4. Pull requests must follow the principles of Object Thinking and Elegant Objects (EO).

Read more in our Contributing Guideline.

Contributor License Agreement

Contributors must sign Teragrep Contributor License Agreement before a pull request is accepted to organization’s repositories.

You need to submit the CLA only once. After submitting the CLA you can contribute to all Teragrep’s repositories.

About

Easy to use CFEngine containers

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages