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.

Sign up for GitHub

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

Jump to bottom

Publish changes from next into main #760

Merged
merged 6 commits into from
Feb 21, 2024
Merged

Publish changes from next into main #760

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
39f0fff
remove future managers and change docker.galasa.dev to docker.io.
CaroMac Feb 21, 2024
50f79b1
update version to registry
CaroMac Feb 21, 2024
cde3d03
Merge pull request #759 from CaroMac/dockerandmanagers
CaroMac Feb 21, 2024
d535031
update next from main
CaroMac Feb 21, 2024
ba66bab
Merge branch 'next' into publishprereq
CaroMac Feb 21, 2024
27ddf14
Merge pull request #761 from CaroMac/publishprereq
CaroMac Feb 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 0 additions & 28 deletions src/markdown-pages/docs/managers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,31 +131,3 @@ Each Manager is tagged with one of the follow readiness indicators:
|
</details>

## Future Managers

| Name | Description |
| ------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
| **AIX Manager** | Provisions AIX server configuration properties, and helps drive provisioning by other Managers such as the OpenStack Manager. |
| **Artifactory Manager** | Provides the ability to retrieve artifacts from Artifactory servers. |
| **CICS z/OS PT Provisioning Manager** | Provisions CICS TS servers for the CICS TS Manager. |
| **GitLab Manager** | Enables tests to retrieve artifacts from GitLab and enables test results to be influenced by the status of issues. |
| **IMS DB Manager** | Provisions and configures IMS DB subsystems. |
| **IMS TM Manager** | Provisions and configures IMS TM subsystems. |
| **ISPF Manager** | Provides a wrapper for the z/OS 3270 Manager to run ISPF sessions. |
| **Liberty Manager** | Provisions and configures Liberty servers. |
| **MongoDB Manager** | Provisions and configures MongoDB databases via Docker containers. |
| **Nexus Manager** | Provides the ability to retrieve artifacts from Nexus servers. |
| **OpenLDAP Manager** | Provides and configures OpenLDAP servers via Docker containers. |
| **RTC Manager** | Enables tests to retrieve artifacts from RTC, and allows test results to be influenced by the status of defects. |
| **TSO Manager** | Provides a wrapper for the z/OS 3270 Manager to run TSO sessions. |
| **UrbanCode Manager** | Provisions and configures UrbanCode servers. |
| **WAS Manager** | Provisions and configures Websphere Application Servers. |
| **Windows Manager** | Provides Windows server configuration properties, driving provisioning by other Managers such as the OpenStack Manager. |
| **WSIM Manager** | Provisions and configures Workload Simulator servers. |
| **z/Linux Manager** | Provides z/Linux server configuration properties, and drives provisioning by other Managers such as the z/VM Manager. |
| **z/OS Connect Manager** | Provides configuration information for z/OS Connect instances, and provisions z/OS Connect instances. |
| **z/OS DB2 Manager** | Providing configuration information to DB2 instances, this Manager also provisions DB2 instances and schemas. |
| **z/OS MQ Manager** | Provisions and configures z/OS MQ subsystems. |
| **z/OS Security Manager** | Creates and maintains userids and profiles in RACF. |
| **z/VM Manager** | Provisions and configures z/VM userids, mainly for provisioning z/OS and z/Linux systems. |
| **ZOWE Manager** | Provides configuration information for and provisions ZOWE instances. |
4 changes: 2 additions & 2 deletions src/markdown-pages/docs/managers/galasa-ecosystem-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,9 +104,9 @@ The following are properties used to configure the Galasa Ecosystem Manager.
| Name: | galasaecosystem.docker.registry |
| Description: | The registry that contains the Docker images |
| Required: | No |
| Default value: | docker.galasa.dev |
| Default value: | docker.io |
| Valid values: | a valid hostname |
| Examples: | <code>galasaecosystem.docker.version=docker.galasa.dev</code> |
| Examples: | <code>galasaecosystem.docker.registry=docker.io</code> |

</details>

Expand Down
2 changes: 1 addition & 1 deletion src/markdown-pages/docs/managers/ipnetwork-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: "IP Network Manager"
**Alpha**

## Overview
The IP Network Manager enables access to applications over TCP/IP networks for those applications whose native communication is over TCP/IP. It can be used by other application specific managers that will build upon the basic address capabilities provided by the IP Network Manager. <br><br> The Manager interrogates the Configuration Properties Store (CPS) to get hostname and port information so that you do not need to hard-code these values into your tests. <br><br> You can view the <a href="https://javadoc.galasa.dev/dev/galasa/ipnetwork/package-summary.html" target="_blank" rel="noopener noreferrer">Javadoc documentation for the Manager here</a>. <br><br>
The IP Network Manager enables access to applications over TCP/IP networks for those applications whose native communication is over TCP/IP. It can be used by other application specific managers that will build upon the basic address capabilities provided by the IP Network Manager. <br><br> The Manager interrogates the Configuration Properties Store (CPS) to get hostname and port information so that you do not need to hard-code these values into your tests. <br><br> You can view the <a href="https://javadoc.galasa.dev/dev/galasa/ipnetwork/package-summary.html" target="_blank" rel="noopener noreferrer">Javadoc documentation for the Manager here</a>. <br><br>



Expand Down
Loading