Release v1.3.0 beta.2 (#255)

* Bugfix/4407/job utility fails on special chars (#208)

* update job utility to avoid direct JSON parsing

* fix job status updates

* update line length for linter

* Update test cases (#207)

Co-authored-by: Asif Mahmud <[email protected]>

* add dependency finder (#210)

* add dependency finder

* update ignore files

* add specific pylint error number

* switch from test ID to ansible-given name

* Enhancement/4365/role doc support (#209)

* Edits to makefile to support doc gen for roles

* Sample role to test doc gen

* Roles RST tie into index.rst

* Role sample and make file updates

* Documentation for makefile target role-doc added

* Updated role doc sample with build sample script and corrected make file

* Added package level checks and script description

* Added logic to check for roles entry in the index.rst

* Removed roles reference from sample in index.rst

* Added newlines to files

* Delete copy of script

* Update example playbook for the sample role

* Lint issue, empty lines was 2

* Added extra messages for better instruction.

* add origin/ to branch name (#212)

* fix newline print if nothing found (#215)

* Bugfix/4660/copy program objects (#213)

* Use -X flag to copy program objects

* Fix typo

Co-authored-by: Asif Mahmud <[email protected]>
Co-authored-by: ddimatos <[email protected]>

* Update template to support complex list with elements (#214)

Signed-off-by: ddimatos <[email protected]>

* Support for choosing parm odering in module template (#220)

Details:

* This change allows selecting whether the input parameter of modules
  are sorted by name or remain ordered as in the source, by modifying
  a boolean variable 'sorted' in the module.rst.j2 file.

Signed-off-by: Andreas Maier <[email protected]>

* Fixed return value formatting issues in module template (#223)

Details:

* If the description was a list with multiple items, only the first item was
  shown and the others were just dropped. This was fixed by showing all items
  of the list.

* The description was not rst_ify'ed, causing formatting strings such as
  'C(xxx)' to appear verbatim. This was fixed by using the rst_ify filter,
  consistent with how it was already done for the description of input
  parameters.

* Nested properties were not always indented correctly (i.e. the desired
  2 blanks per level). Fixed that.

* The 'type:' item was indented some blanks more than the other attributes
  of a property. Fixed that by indenting it with the same number of blanks
  as the other attributes.

* For samples that are not str or int, the code_block statement and the
  following sample data item are not indented variably by level, but by
  a fixed number of blanks in the generated rst. This causes them to be
  rendered inconsistent as soon as the nesting level of the properties
  is more than 4 or so. Fixed that by indenting them by level.

* The top level of return properties was already indented one level.
  This is not a real problem, but inconsistent with how it is done for
  input parameters, and when looking at the generated rst file with a
  browser, grey vertical bars are shown due to that. Fixed that by
  changing the initial level from 1 to 0, consistent with input parms.

* There were many trailing blanks. Not a real problem, but somehow
  inconvenient in git with editors that strip them. Fixed that by
  letting all control constructs begin at the begin of the line
  instead of indenting them according to their control nesting
  level. The control nesting level is still maintained but within
  the curly braces of the control construct.

Signed-off-by: Andreas Maier <[email protected]>

* Fixes #224: Support for multiple samples in module return properties (#225)

* Fixed return value formatting issues in module template

Details:

* If the description was a list with multiple items, only the first item was
  shown and the others were just dropped. This was fixed by showing all items
  of the list.

* The description was not rst_ify'ed, causing formatting strings such as
  'C(xxx)' to appear verbatim. This was fixed by using the rst_ify filter,
  consistent with how it was already done for the description of input
  parameters.

* Nested properties were not always indented correctly (i.e. the desired
  2 blanks per level). Fixed that.

* The 'type:' item was indented some blanks more than the other attributes
  of a property. Fixed that by indenting it with the same number of blanks
  as the other attributes.

* For samples that are not str or int, the code_block statement and the
  following sample data item are not indented variably by level, but by
  a fixed number of blanks in the generated rst. This causes them to be
  rendered inconsistent as soon as the nesting level of the properties
  is more than 4 or so. Fixed that by indenting them by level.

* The top level of return properties was already indented one level.
  This is not a real problem, but inconsistent with how it is done for
  input parameters, and when looking at the generated rst file with a
  browser, grey vertical bars are shown due to that. Fixed that by
  changing the initial level from 1 to 0, consistent with input parms.

* There were many trailing blanks. Not a real problem, but somehow
  inconvenient in git with editors that strip them. Fixed that by
  letting all control constructs begin at the begin of the line
  instead of indenting them according to their control nesting
  level. The control nesting level is still maintained but within
  the curly braces of the control construct.

Signed-off-by: Andreas Maier <[email protected]>

* Support for multiple samples in module return properties

Details:

* The module.rst.j2 template supported only a single sample in the 'sample'
  attribute of a return property. This change adds support for multiple
  samples by specifying child attributes 'sample1', 'sample2', etc under
  the 'sample' attribute. This is consistent with how the ibm_zosmf
  collection supports it, but the solution in addition takes care to
  distinguish str/int types and complex types consistent with how it
  is done for single samples.

Signed-off-by: Andreas Maier <[email protected]>

Co-authored-by: ddimatos <[email protected]>

* Fixes #226: Support for showing list elements in module return values (#227)

* Fixed return value formatting issues in module template

Details:

* If the description was a list with multiple items, only the first item was
  shown and the others were just dropped. This was fixed by showing all items
  of the list.

* The description was not rst_ify'ed, causing formatting strings such as
  'C(xxx)' to appear verbatim. This was fixed by using the rst_ify filter,
  consistent with how it was already done for the description of input
  parameters.

* Nested properties were not always indented correctly (i.e. the desired
  2 blanks per level). Fixed that.

* The 'type:' item was indented some blanks more than the other attributes
  of a property. Fixed that by indenting it with the same number of blanks
  as the other attributes.

* For samples that are not str or int, the code_block statement and the
  following sample data item are not indented variably by level, but by
  a fixed number of blanks in the generated rst. This causes them to be
  rendered inconsistent as soon as the nesting level of the properties
  is more than 4 or so. Fixed that by indenting them by level.

* The top level of return properties was already indented one level.
  This is not a real problem, but inconsistent with how it is done for
  input parameters, and when looking at the generated rst file with a
  browser, grey vertical bars are shown due to that. Fixed that by
  changing the initial level from 1 to 0, consistent with input parms.

* There were many trailing blanks. Not a real problem, but somehow
  inconvenient in git with editors that strip them. Fixed that by
  letting all control constructs begin at the begin of the line
  instead of indenting them according to their control nesting
  level. The control nesting level is still maintained but within
  the curly braces of the control construct.

Signed-off-by: Andreas Maier <[email protected]>

* Support for showing list elements in module return values

Details:

* Currently, the module.rst.j2 template does not show the 'elements'
  attribute for return value properties. It does show it for input
  parameters.

  This change adds support for showing the 'elements' attribute for return
  value properties, if specified.

Signed-off-by: Andreas Maier <[email protected]>

Co-authored-by: ddimatos <[email protected]>

* Fixes #228: Support for multi-line JSON samples in module template (#229)

* Fixed return value formatting issues in module template

Details:

* If the description was a list with multiple items, only the first item was
  shown and the others were just dropped. This was fixed by showing all items
  of the list.

* The description was not rst_ify'ed, causing formatting strings such as
  'C(xxx)' to appear verbatim. This was fixed by using the rst_ify filter,
  consistent with how it was already done for the description of input
  parameters.

* Nested properties were not always indented correctly (i.e. the desired
  2 blanks per level). Fixed that.

* The 'type:' item was indented some blanks more than the other attributes
  of a property. Fixed that by indenting it with the same number of blanks
  as the other attributes.

* For samples that are not str or int, the code_block statement and the
  following sample data item are not indented variably by level, but by
  a fixed number of blanks in the generated rst. This causes them to be
  rendered inconsistent as soon as the nesting level of the properties
  is more than 4 or so. Fixed that by indenting them by level.

* The top level of return properties was already indented one level.
  This is not a real problem, but inconsistent with how it is done for
  input parameters, and when looking at the generated rst file with a
  browser, grey vertical bars are shown due to that. Fixed that by
  changing the initial level from 1 to 0, consistent with input parms.

* There were many trailing blanks. Not a real problem, but somehow
  inconvenient in git with editors that strip them. Fixed that by
  letting all control constructs begin at the begin of the line
  instead of indenting them according to their control nesting
  level. The control nesting level is still maintained but within
  the curly braces of the control construct.

Signed-off-by: Andreas Maier <[email protected]>

* Support for multiple samples in module return properties

Details:

* The module.rst.j2 template supported only a single sample in the 'sample'
  attribute of a return property. This change adds support for multiple
  samples by specifying child attributes 'sample1', 'sample2', etc under
  the 'sample' attribute. This is consistent with how the ibm_zosmf
  collection supports it, but the solution in addition takes care to
  distinguish str/int types and complex types consistent with how it
  is done for single samples.

Signed-off-by: Andreas Maier <[email protected]>

* Support for multi-line JSON samples in module template

Details:

* The current module template generates long single-line JSON representations
  of sample values of return value properties. This change formats them
  as multi-line JSOn with an indentation of 4.

* The code-block used for these JSOn samples is marked up to have json content,
  producing a nicer coloring of the samples.

Signed-off-by: Andreas Maier <[email protected]>

Co-authored-by: ddimatos <[email protected]>

* Add support to template to skip options that begin with an underscore

Signed-off-by: ddimatos <[email protected]>

* Remove depreated ansible_metadata blocks from all modules per Ansibles new requirements (#235)

Signed-off-by: ddimatos <[email protected]>

* Update/create new issue templates (#236)

* Update/create new issue templates

Adding three new templates:
- Bug report
- Feature request
- Documentation report

* Update template with shoter headings

Update with shorter headings and uppercase

* Updated issue topics and made them uppercase

* Renamed Documentation URL to just URL

* Uppercase Screenshots

* Template updates

Signed-off-by: ddimatos <[email protected]>

* Renamed documentation-report.md to documentation_report.md

Signed-off-by: ddimatos <[email protected]>

* Improve template comments.

Signed-off-by: ddimatos <[email protected]>

* Updated build_ignore for Ansible 2.10 readiness and additional updates (#237)

Signed-off-by: ddimatos <[email protected]>

* Update README to standardize across collections (#238)

* Update README to standardize across collections

Signed-off-by: ddimatos <[email protected]>

* Update year on copyright

Signed-off-by: ddimatos <[email protected]>

* Updated all licenses to use verbose declaration of apache v2 lic (#239)

Signed-off-by: ddimatos <[email protected]>

* add jenkinsfile (#240)

* Update module documentation to provide a better flow to the user (#243)

Signed-off-by: ddimatos <[email protected]>

* update ping module with empty options as newest ansible-doc-extrator requires it (#242)

Signed-off-by: ddimatos <[email protected]>

* Added Jenkinsfile to the ignore to exclude from collection builds (#241)

Signed-off-by: ddimatos <[email protected]>

* adding Blake's test change, and Rich's script change to a clean dev pull (#244)

* Enhancement/3729 (#247)

* initial pre-testing commit.  Interface changes and basic rexx script are there.

* got basic playbooks working.  Changed command to 1-line.
Added surrounding quotes for neatness

* corrected bad assumption about sdsf isexec operators.
switched to checking first word of command.
it now appears to pass existing pytests.

* Corrected reported PEP8 errors

* responses to review commends on 12/7-12/8
corrected documentation typo
added a little extra info on verbose, security fields
changes to rexx script:
  - removed usage calls.  Added usage info as comment to the python
  - added (WAIT) or (VERBOSE WAIT) to fully implement the delay feature
  - switched to user arg for the fixed position parameters
  - renamed 'dumpit' to 'showoutput' (sorry)

* removed reset option, based on discussion with onno
also added more output detail based on verbose and security options

* removed comment with too many leading octothorps

* responses to review:
  + consolidates -v and -s options
  + eliminated -d option
  + added 'rapid' req=false def=true to use delay as timeout
  + if 'rapid'=false, delay is "wait" for full time
  + delay=0 will now ignore delay
  + function tests updated to try 5 rapid and 7 non-rapid
  + documentation updated

* Changes based on review:
  + changed time variables to wait_time_s and wait
  + added actual time evaluation to the test cases

* Fixed bad indent on 'wait' documentation

* fixed doc line referring to 0

* Correct long lines in doc

Signed-off-by: ddimatos <[email protected]>

* removed debug entries from data in unit tests
added missing dependancy check file

* changed test 5 to not be a duplicate of test 3...mistake from removing 'debug'

* corrected bug in rexx script used for opercmd
changed args from 'arg' to positions, to reconcile command issues

* updated operator to allow for error returns leaving changed as false
.. previously it was always setting the return the changed=true

* added shebang to a docs file

* added new error condition to handle command errors
  it turns out running a rexx script returns 0 if the rexx succeeds
  so I'm checking that at least 3 lines came back
  also checking that the third line doesn't have invalid or error

* typo fix: missed a parenthesis.

* typo fix (note in)

* continuing the typo patrol

* changed scan for 'invalid' to account for 'running' line of output
  (scan was off by 1 line)

* added error conditions as json fails for invalid/error notes

* added explicit exception text for test purposes (mfj doesn't do this?!)

* Moved 'running' line to end and called 'ran', to see if it fixes the jobId issue

* change to better_arg_parser to handle more complex encoding arguments,
specifically for ANSI_X3.4-1968

* Revert "added explicit exception text for test purposes (mfj doesn't do this?!)"

This reverts commit 7ff0955.
alse removed change to [email protected]'t fix issue

* Added condition for when action call includes a starting slash

* added time to test_zos_operator_positive_verbose_with_quick_delay
it was failing on too small of a time difference

* still messing with the time-based test.

* changed error testing loop to handle possible null/none cases
changed error checking to iterate the first 5 lines of each output type,
  so we're not dependant on a fixed response position.

* corrected operator-command-error, where composite message was still needed

* Added comments to describe the new error detection logic
Added explanations of the 5, 2 and internal variables

* corrected the documentation so it doesn't say "JCL"
added 'unidentifiable' as an additional error status return

Co-authored-by: ddimatos <[email protected]>

* Update bug template with version request

Added requests for version and additional detail.

* Update requirements_managed.rst (#248)

* Update requirements_managed.rst

Reorganized content for core managed requirments

* Update requirements_managed.rst

Moved the links about playbook configuration to reorganize content

* Update playbooks.rst

moved links about playbook basics to this topic from the requirements topic

* Update requirements_managed.rst

removed playbook links

* return stderr if not empty (#249)

* Enhancement/3688b (#246)

* added pre-filter to job_submit to eliminate carriage returns before converting to EBCDIC

* added changes for BetterArgParser & NAZARE-4835:
  + Added recognition of '.' and '..'.
  + Centralized pathing for 2 functions.
  + Changed choice processor to handle case-mismatches.

* rebuilt 3688 pulling from dev instead of master for root
  + change to zos_job_submit to pre-filter \r from incoming text files
  + 4835 change to better_arg_parser to process '.' and '..'
  + 4835 change to better_arg_parser to allow case-correction on choice arg types

* Correction after saving change to wrong local branch
  + zos_job_submit should now have the correct changes
  + it appears better_arg_parser was saved correctly

* updated a test module that was misbehaving.

* discovered test_zos_copy.py was legacy...re-committing with correction

* commented out first data case on test_argument_parsing_unix_failure_path
This is because new local_path resolves "../u..." correctly, so won't throw expected ValueError

* Removed case-unsensitive 'casefold' from better arg parser
This is because multiple other module tests are dependant on case-sensitive arg rejection

* change to test of better arg parser to not look at .. value, since that now works

* change to use -c option on iconv call, to see if that resolves cr issue

* added test for extra \r to the pytest system

* added match/no match info into job.py

* changed regex to accomodate potential leading spaces, which duplicated the issue
removed tracing print statements

* added error handler/raise to _parse_jobs, enhanced completion_messages search string

* changed job parse_job to is not none ... this make move to a runtime error
altered zos_job_submit to verify I'm seeing the correct string trigger

* cleaned error message in job.py
removed previous filter code from zos_job_submit
unless the error starts triggering again, this is a final build

* added readable vs unreadable to job task

* added nonetypoe prodection to _parse_dds in job.py (second nonetype crash)

* removed  quotes in the doc for 'block' (#250)

* Updated requirements for managed node doc

Signed-off-by: ddimatos <[email protected]>

* Updated managed nod doc with target keyword

Signed-off-by: ddimatos <[email protected]>

* Update requirements single doc with streamlined doc to better map to other updated docs

Signed-off-by: ddimatos <[email protected]>

* Clean up playbooks doc bullets that had extra spaces

Signed-off-by: ddimatos <[email protected]>

* Update release notes for v1.3.0-beta.2

Signed-off-by: ddimatos <[email protected]>

* Update modules doc to reduce unnecessary ansible-doc reference

Signed-off-by: ddimatos <[email protected]>

* Update doc gen conf to remove the prev and next buttons

Signed-off-by: ddimatos <[email protected]>

* Generate all module docs with the updated module.rst.j2 template

Signed-off-by: ddimatos <[email protected]>

* Update release_notes.rst

Minor doc fixes

* Unfied doc consistency change for Ansible core content. (#253)

* Update ansible content page with trademarks and scope

Signed-off-by: ddimatos <[email protected]>

* Update with links and zoau reference

Signed-off-by: ddimatos <[email protected]>

* Updated release notes with clearer job utility description and a playbook bug

Signed-off-by: ddimatos <[email protected]>

* Fix pep8 missing indentation or outdented

Signed-off-by: ddimatos <[email protected]>

* Fix pep8 missing indentation or outdented v2

Signed-off-by: ddimatos <[email protected]>

* Correct MD style link found in RST style

Signed-off-by: ddimatos <[email protected]>

Co-authored-by: Blake Becker <[email protected]>
Co-authored-by: Asif Mahmud <[email protected]>
Co-authored-by: Asif Mahmud <[email protected]>
Co-authored-by: Andreas Maier <[email protected]>
Co-authored-by: Rich Parker <[email protected]>
Co-authored-by: RadhaV2020 <[email protected]>
Co-authored-by: balkajbaf <[email protected]>

Author: 8 people

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,108 @@
+---
+name: Bug report
+about: Create a bug report to share a problem with a module, plugin, task or feature
+title: "[Bug] Report module, plugin, task or feature bugs"
+labels: 'Type: Bug'
+assignees: ''
+
+---
+
+<!--- Verify first that your issue is not already reported on GitHub. -->
+<!--- Also, test if the latest release in Galaxy is experiencing the same bug. -->
+<!--- Note: If the reviewer determines this is a dependency related bug such as
+      IBM Z Open Automation Utilities (ZOAU), it will be stated in the issue,
+      the issue will be closed and will require that the reporter of the issue
+      follow the dependencies process to report bugs.
+-->
+<!--- Complete sections below as described. -->
+
+##### SUMMARY
+<!--- Explain the problem briefly below. -->
+<!--- Example; when using module zos_xyz with options ABC I receive this
+      message "some msg" , yet when I run the same scenario on x3270 it
+      is successful.
+-->
+
+##### COMPONENT NAME
+<!--- Specify the name of the module, plugin, task or feature you are
+      experiencing a bug with if it applies.
+-->
+
+##### ANSIBLE VERSION
+<!--- Paste verbatim output from "ansible --version" between quotes. -->
+```
+Ansible version output:
+```
+
+##### SPECIFY ANSIBLE COLLECTION VERSION
+<!--- If you do not know the version or want to verify, you can use the
+      command below to extract the collection version; replace PATH_PREFIX
+      with where you installed the collection. Default is installation path is:
+      `~/.ansible/collections/ansible_collections/ibm/ibm_zos_core`.
+
+      `cat PATH_PREFIX/ibm/ibm_zos_core/MANIFEST.json | grep version
+-->
+
+##### SPECIFY THE Z OPEN AUTOMATION UTILITIES VERSION
+<!-- If you do not know the version of ZOAU, you can run the version
+     command on the target: `zoaversion -b`
+-->
+
+##### ENVIRONMENT
+<!--- Provide all relevant information below, e.g. target z/OS version, network
+      device firmware, etc.
+-->
+
+##### STEPS TO REPRODUCE
+<!--- Describe how to reproduce the problem, using a minimal test-case
+      or paste example playbook/yaml between below.
+-->
+<!--- For example:
+         1. Enter command  '...'
+         2. Press enter  '....'
+         3. Scroll down to '....'
+         4. See error '....'
+-->
+```yaml
+Reproduction playbook/yaml
+```
+
+##### EXPECTED RESULTS
+<!--- Describe what you expected to happen. -->
+
+
+##### ACTUAL RESULTS
+<!--- Describe what actually happened. If possible run with extra
+      verbosity (-vvvv). An example of playbook with extra verbosity
+      ansible-playbook -i <inventory> <playbook> -vvvv
+-->
+
+<!--- Paste verbatim command output between quotes. -->
+```
+Playbook output:
+```
+
+##### CONFIGURATION
+#### Ansible.cfg
+<!--- Paste verbatim output from "ansible-config dump --only-changed" or
+      contents from `ansible.cfg`.  -->
+```
+'ansible-config dump --only-changed' output:
+```
+
+#### Inventory
+<!--- Paste the contents of the inventory file removing any sensitive
+      information. -->
+```
+Inventory content:
+```
+
+#### Vars
+<!--- Paste the contents of group_vars or host_vars file removing any
+      sensitive information. -->
+```
+'group_vars' or 'host_vars' content:
+```
+
+##### SCREENSHOTS
+<!--- If applicable, add screenshots to help explain your problem. -->

.github/ISSUE_TEMPLATE/documentation_report.md

@@ -0,0 +1,45 @@
+---
+name: Documentation report
+about: Report documentation errors or changes
+title: "[Documentation] Describe the documentation report"
+labels: 'Type: Documentation'
+assignees: ''
+
+---
+
+<!--- Complete sections below as described. -->
+
+##### URL
+<!--- Include the URL to the documentation page the issue is open for. -->
+
+##### SUMMARY
+<!--- A clear and concise description if it is a documentation bug. -->
+<!--- A clear and concise description of the change, enhancement or suggestion. -->
+<!--- If applicable, reproduction steps such as:
+                   Go to page '...'
+                   Click on link '....'
+                   Scroll down to '....'
+                   See error '....' or Here is a good place for '....'
+-->
+
+##### OUTPUT
+<!--- If the documentation instructions caused an error, share the output
+      of the error.
+-->
+
+##### SCREENSHOT
+<!--- If applicable, add screenshots to help explain your problem. -->
+
+##### BROWSER
+<!--- Share the browser and version if this is a documentation bug.
+        Browser [e.g. Firefox, safari, chrome]
+        Version [e.g. 22, FF ESR 78.6]
+-->
+<!--- If this is found on a smart phone; share the device information.
+        Device: [e.g. iPhone6]
+        Browser [e.g. Firefox, safari, chrome]
+        Version [e.g. 22, FF ESR 78.6]
+ -->
+
+##### ADDITIONAL
+<!--- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,49 @@
+---
+name: Feature request
+about: Suggest a new feature or enhancement to an existing function
+title: "[Feature] Short desciption or feature title"
+labels: 'Type: Enhancement, Type: Feature'
+assignees: ''
+
+---
+
+<!--- Verify first that your feature was not already discussed on
+      [GitHub}(https://github.com/ansible-collections/ibm_zos_core/issues).
+-->
+<!--- Complete sections below as described. -->
+
+##### FEATURE
+<!--- If applicable, the name of the module, plugin, task or new feature the
+      request should be added to.
+      Example:
+        - Collection ibm_zos_core could benefit with a module
+          (zos_chksum) that can....
+        - Module zos_data_set could benefit from an option `dynamic_extents`
+          that can....
+-->
+
+##### USE CASE
+<!-- Is your feature request related to a problem? Describe the use case:
+     - Who is the persona? System programmer, system admin, devOps, etc
+     - What does the user want to do? Manage resource XYZ, submit ABC, etc
+     - The user's goal: Automate the daily task that such that XYZ ....
+     - The steps the user takes to accomplish a particular task:
+        1. User logs in to...
+        2. User copies ....
+        3. User edits ...
+        4. User submits...
+-->
+
+##### SUMMARY
+<!--- Describe the new feature/improvement briefly below. -->
+
+##### DESIGN
+<!---  Share any implementations, designs, snippets or playbooks you have for
+       this feature.
+-->
+
+##### ALTERNATIVES
+<!--- A clear and concise description of any alternative solutions or
+     features you've considered.
+-->
+

Jenkinsfile

@@ -0,0 +1,5 @@
+stage('Run z/OS Ansible Pipeline') {
+    build job: 'zosAnsible', parameters:[
+        string(name: 'BRANCH', value: CHANGE_BRANCH),
+    ]
+}

README.md

@@ -1,59 +1,63 @@
 IBM z/OS core collection
 ========================
 
-The **IBM z/OS core collection**, also represented as **ibm\_zos\_core**
-in this document, is part of the broader offering **Red Hat® Ansible
-Certified Content for IBM Z**. IBM z/OS core collection supports tasks
-such as creating data sets, submitting jobs, querying jobs,
-retrieving job output, encoding data sets, fetching data sets, operator
-commands, TSO commands, ping and querying operator actions.
-
-The **IBM z/OS core collection** serves as a dependency for other collections
-under the **Red Hat® Ansible Certified Content for IBM Z** umbrella and
-works closely with offerings such as
-[IBM z/OS IMS collection](https://galaxy.ansible.com/ibm/ibm_zos_ims)
-to deliver a solution that will enable you to automate tasks on z/OS subsystems
-such as IMS.
+The **IBM z/OS core collection**, also represented as
+**ibm_zos_core** in this document, is  part of the broader
+initiative to bring Ansible Automation to IBM Z® through the offering
+**Red Hat® Ansible Certified Content for IBM Z®**. The
+**IBM z/OS core collection** supports automation tasks such as
+creating data sets, submitting jobs, querying jobs,
+retrieving job output, encoding data sets, fetching data sets, copying data
+sets, executing operator commands, executing TSO commands, ping,
+querying operator actions, APF authorizing libraries,
+editing textual data in data sets or Unix System Services files,
+finding data sets, backing up and restoring data sets and
+volumes and running z/OS programs without JCL.
+
 
 Red Hat Ansible Certified Content for IBM Z
 ===========================================
 
 **Red Hat® Ansible Certified Content for IBM Z** provides the ability to
-connect IBM Z® to clients\' wider enterprise automation strategy through
-the Ansible Automation Platform ecosystem. This enables development and
-operations automation on Z through a seamless, unified workflow
-orchestration with configuration management, provisioning, and
-application deployment in one easy-to-use platform.
-
-IBM z/OS core collection, as part of the broader offering **Red Hat®
-Ansible Certified Content for IBM Z**, is available on both, **Galaxy**
-as community supported and **Automation Hub** with enterprise support.
-
-For **guides** and **reference**, please visit [the documentation
-site](https://ibm.github.io/z_ansible_collections_doc/index.html).
+connect IBM Z® to clients' wider enterprise automation strategy through the
+Ansible Automation Platform ecosystem. This enables development and operations
+automation on Z through a seamless, unified workflow orchestration with
+configuration management, provisioning, and application deployment in
+one easy-to-use platform.
+
+The **IBM z/OS core collection** is following the
+**Red Hat® Ansible Certified Content for IBM Z®** method of distributing
+content. Collections will be developed in the open, and when content is ready
+for use it is released to
+[Ansible Galaxy](https://galaxy.ansible.com/search?keywords=zos_&order_by=-relevance&deprecated=false&type=collection&page=1)
+for community adoption. Once contributors review community usage, feedback,
+and are satisfied with the content published, the collection will then be
+released to [Ansible Automation Hub](https://www.ansible.com/products/automation-hub)
+as **certified** and **IBM supported** for
+**Red Hat® Ansible Automation Platform subscribers**.
+
+
+For guides and reference, please review the [documentation](https://ibm.github.io/z_ansible_collections_doc/index.html).
 
 Features
 ========
-
-The IBM z/OS core collection includes
-[connection plugins](https://github.com/ansible-collections/ibm_zos_core/tree/master/plugins/connection/),
-[action plugins](https://github.com/ansible-collections/ibm_zos_core/tree/master/plugins/action/),
-[modules](https://github.com/ansible-collections/ibm_zos_core/tree/master/plugins/modules/),
-[sample playbooks](https://github.com/ansible-collections/ibm_zos_core/tree/master/playbooks/),
-[filters](https://github.com/ansible-collections/ibm_zos_core/tree/master/plugins/filter/),
+The **IBM z/OS core collection**, includes
+[connection plugins](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/plugins.html#connection),
+[action plugins](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/plugins.html#action),
+[modules](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/modules.html),
+[filters](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/filters.html),
+[sample playbooks](https://ibm.github.io/z_ansible_collections_doc/playbooks/playbooks.html)
 and ansible-doc to automate tasks on z/OS.
 
 Copyright
 =========
-
-© Copyright IBM Corporation 2020
+© Copyright IBM Corporation 2020-2021.
 
 License
 =======
-
 Some portions of this collection are licensed under [GNU General Public
 License, Version 3.0](https://opensource.org/licenses/GPL-3.0), and
 other portions of this collection are licensed under [Apache License,
-Version 2.0](https://opensource.org/licenses/Apache-2.0).
+Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
 
-See individual files for applicable licenses.
+See individual files for applicable licenses.