OHS Base YAML install file #103
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
November 12, 2024 11:32
I am trying manually work around https://github.com/spm-devops/transformers/issues/1327 - until this is fixed. On a VM i can manually install all the required pieces i.e. OHS Base OHS 19c Upgrade OHS 19c latest patches However manually it is more difficult to complete the OHS config for Curam - as this has a number of steps including creating SSL certs etc. To help this I have created a YAML file to just install the Base version of OHS. This will mean when i choose this version when deploying a VM - it will in stall the base and configure OHS for use with Curam.. I can then manually install the 19c upgrade and latest patches - and OHS should be automatically configured for me (from the base install) This changeset has a YAML file which just installs the Base version (commented out the patches information). There is a change needed to the ohs main yaml file - to only Patch OHS when the ohs_version variable is set - which it should be for all other yamls (outside of the base) Tested this locally on molecule - and it looks to pass for both the Base install and latest 12c fixpacks.. If this works will be first step in trying to solve the above transformers ticket.
Update main.yaml - add in original when check
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am trying manually work around https://github.com/spm-devops/transformers/issues/1327 - until this is fixed.
On a VM i can manually install all the required pieces i.e. OHS Base
OHS 19c Upgrade
OHS 19c latest patches
However manually it is more difficult to complete the OHS config for Curam - as this has a number of steps including creating SSL certs etc.
To help this I have created a YAML file to just install the Base version of OHS. This will mean when i choose this version when deploying a VM - it will in stall the base and configure OHS for use with Curam.. I can then manually install the 19c upgrade and latest patches - and OHS should be automatically configured for me (from the base install)
This changeset has a YAML file which just installs the Base version (commented out the patches information). There is a change needed to the ohs main yaml file - to only Patch OHS when the ohs_version variable is set - which it should be for all other yamls (outside of the base)
Tested this locally on molecule - and it looks to pass for both the Base install and latest 12c fixpacks..
If this works will be first step in trying to solve the above transformers ticket.