Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor as an Ansible collection #248

Closed
wants to merge 1 commit into from

Conversation

GreenCappuccino
Copy link

@GreenCappuccino GreenCappuccino commented Oct 25, 2023

A relatively barebones attempt at a refactor of the project into an Ansible collection.


Tests

  • flake8
  • mypy
  • unittests
  • el8-functional
  • el9-functional

I'm currently having issues with vagrant on my machine. Will get back to the functional tests later.

GitHub Workflows:

  • ansible-lint
  • check-trailing-whitespaces

Needs to be fixed before merge:

  • RPM spec file changes

Should be fixed after merge; in my opinion, out of scope:

  • Replace note about collections in doc/source/index.rst
  • Determine compatibility with more recent versions of Ansible

I've tested the preflight playbook and bootstrap and orchestration modules to work on my playbooks and installation of AWX. I am currently using my fork in my AWX installation for further testing. Further work is needed to finalize this PR. Apologies for any inconvenience, I'm rather new to Ansible.

Not sure if the namespace and name for the collection I chose is appropriate.


Should fix #246. Supercedes #247.

@GreenCappuccino
Copy link
Author

Whatever I do, I just can't seem to get the vagrant cluster up. 😕

@guits
Copy link
Collaborator

guits commented Oct 30, 2023

hi @GreenCappuccino
This is something I had started to do here but for some reason I had to put it on the back burner.
Glad to see someone is still interested in that topic 🙂

Whatever I do, I just can't seem to get the vagrant cluster up. 😕

are you referring to this error ?

ERROR! the playbook: /home/jenkins-build/build/workspace/cephadm-ansible-prs-el8-functional/cephadm-preflight.yml could not be found

Comment on lines +1 to +162

# Flask stuff:
instance/
.webassets-cache

# Scrapy stuff:
.scrapy

# Sphinx documentation
docs/_build/

# PyBuilder
.pybuilder/
target/

# Jupyter Notebook
.ipynb_checkpoints

# IPython
profile_default/
ipython_config.py

# pyenv
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version

# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock

# poetry
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
# This is especially recommended for binary packages to ensure reproducibility, and is more
# commonly ignored for libraries.
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
#poetry.lock

# pdm
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
#pdm.lock
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
# in version control.
# https://pdm.fming.dev/#use-with-ide
.pdm.toml

# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
__pypackages__/

# Celery stuff
celerybeat-schedule
celerybeat.pid

# SageMath parsed files
*.sage.py

# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/

# Spyder project settings
.spyderproject
.spyproject

# Rope project settings
.ropeproject

# mkdocs documentation
/site

# mypy
.mypy_cache/
.dmypy.json
dmypy.json

# Pyre type checker
.pyre/

# pytype static type analyzer
.pytype/

# Cython debug symbols
cython_debug/

# PyCharm
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
# and can be added to the global gitignore or merged into this file. For a more nuclear
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
.idea/

.vagrant
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's true the project doesn't have a .gitignore, I'm not against adding one but I would prefer we don't introduce "custom ignores"

@asm0deuz asm0deuz closed this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Playbooks do not run as an AWX project
3 participants