db2

.gitignore

@@ -1,3 +1,117 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
 
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+my_env/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+tests/output/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# pyenv
+.python-version
+
+# celery beat schedule file
+celerybeat-schedule
+
+# 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/
+
+# JetBrains
+.idea/
+
+# Ansible sensitive
+hosts
+play.yml
+ansible_collections
 .DS_Store
-.DS_Store
+bin/
+

.travis.yml

@@ -27,10 +27,10 @@ install:
 
 env:
   global:
-    - OCTOKIT_API_ENDPOINT=https://github.ibm.com/api/v3/
-    - ANSIBLE_GALAXY_SERVER_LIST=CIO
-    - ANSIBLE_GALAXY_SERVER_CIO_URL=https://galaxy.ansible.com/
-    # ANSIBLE_GALAXY_SERVER_CIO_TOKEN is set using secure environment variables
+    - OCTOKIT_API_ENDPOINT=https://api.github.com/
+    - ANSIBLE_GALAXY_SERVER_LIST=IBM
+    - ANSIBLE_GALAXY_SERVER_IBM_URL=https://galaxy.ansible.com/
+    # ANSIBLE_GALAXY_SERVER_IBM_TOKEN is set using secure environment variables
   matrix:
     - SCENARIO=default
 
@@ -74,4 +74,4 @@ jobs:
           file: "./$COLLECTION_NAMESPACE-$COLLECTION_NAME-$COLLECTION_VERSION.tar.gz"
           skip_cleanup: true
           on:
-            branch: master
+            branch: main

CONTRIBUTING.md

@@ -75,11 +75,13 @@ The playbook directory should contain the following:
 
 Creating a new collection is quite simple:
 
-* Create a new repository from [WH-GovSPM-Internal/ansible_collection_template](https://github.ibm.com/WH-GovSPM-Internal/ansible_collection_template/generate)
+* Create a new repository from `Coming Soon!`
 * Update the `README.md` and `galaxy.yml` files to match your desired namespace and collection name
 
 To enable the Travis, set the following variables:
 
-* `ANSIBLE_GALAXY_SERVER_CIO_TOKEN` - [CIO Galaxy](https://galaxy.containers.ciocloudservices.ibm.com/me/preferences) API Key
+* `ANSIBLE_GALAXY_SERVER_CIO_TOKEN` - [Galaxy](https://galaxy.ansible.com/me/preferences) API Key
 * `GITHUB_OAUTH_TOKEN` - GitHub Personal Access Token for tagging/publishing release
-* `EUSWG_TOKEN` - Artifactory API Token, if required for your roles/playbooks
+* `ARTIFACTORY_TOKEN` - Artifactory API Token, if required for your roles/playbooks
+* `ARTIFACTORY_URL` - Artifactory URL, if required for your roles/playbooks
+* `ARTIFACTORY_REPO` - Artifactory REPO, if required for your roles/playbooks

README.md

@@ -1,2 +1,43 @@
-# ansible-spm-middleware
-A collection of Middleware modules and roles required for installing Cúram Social Program Management. SUITABLE FOR INTERNAL TEST AND DEVELOPMENT ONLY
+# Ansible Collection for SPM Middleware
+
+## MUST BE CHANGED AFTER REPO IS CREATED
+
+* Entries in `galaxy.yml` should point to correct locations
+* Molecule config and plays should point to correct collection
+    - molecule/default/converge.yml
+
+## Overview
+
+Collections are a distribution format for Ansible content. You can use collections to package and distribute playbooks, roles, modules, and plugins.
+You can publish and use collections through `Ansible Galaxy <https://galaxy.ansible.com/ibm>`.
+
+Assumption for having collection as a repo, is it enable reuse of content as well, such repo can be easily used separately by just adding `ansible.cfg`.
+
+## Collection structure
+
+Collections follow a simple data structure. None of the directories are required unless you have specific content that belongs in one of them. A collection does require a ``galaxy.yml`` file at the root level of the collection. This file contains all of the metadata that Galaxy
+and other tools need in order to package, build and publish the collection::
+
+    collection/
+    ├── docs/
+    ├── galaxy.yml
+    ├── plugins/
+    │   ├── modules/
+    │   │   └── module1.py
+    │   ├── inventory/
+    │   └── .../
+    ├── README.md
+    ├── roles/
+    │   ├── role1/
+    │   ├── role2/
+    │   └── .../
+    ├── playbooks/
+    │   ├── files/
+    │   ├── vars/
+    │   ├── templates/
+    │   └── tasks/
+    └── tests/
+
+### Useful links
+
+* https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html