Create a GitHub organization.
Create a GitHub personal access token.
Create your GitHub repositories.

Navigate to GitHub.
Click the profile icon on the right side and click
Settings
.
Click the
Organizations
tab.
Click
New organization
.
Provide a name for your organization account and click
Next
.
Click
Complete setup
or
Skip this step
to continue.

Navigate to GitHub.
Click the
Profile
icon on the right side and click
Settings
.
Click the
Developer settings
tab.
Click the
Personal access tokens
tab.
Click
Generate a new token
.
Enter a name for your token in the
Note
field.
Select the
Repo
checkbox.
Click
Generate token
.

GitHub repository for approved orders:
Kyndryl Modern Operations Applications uses a separate repository for approved orders to ensure that your DevOps pipelines/infrastructure is not triggered for any release/deployment request commits that have not been approved by the correct owners in Kyndryl Modern Operations Applications. This repository will be used to commit information related
only
to orders that have been approved in Kyndryl Modern Operations Applications. Your pipelines can use Kyndryl Modern Operations Applications to process the request.
GitHub repository for GitOps content and submitted orders not yet approved:
Kyndryl Modern Operations Applications uses this repository for GitOps content and for submitted orders that have not been approved yet. This repository is used for these operations:
Ingesting request forms used for your GitOps/DevOps deployment workflows into Kyndryl Modern Operations Applications.
Committing information related to orders that have been approved in GitHub.
Order tracking information for GitOps should not be committed by your pipelines to the repository used for approved orders because this action would trigger an unwanted commit webhook to your deployment pipelines.

Navigate to GitHub.
Click the profile icon on the right side and click
Settings
.
Click the
Repositories
tab.
Click
Create one
.
Provide a name for your repository.
Provide an optional description.
Select whether the repository will be
Private
or
Public
.
Select the
Initialize this repository with a README
checkbox, if wanted.
Click
Create repository
.

GitHub repository for approved orders repository:
Create a branch called
RELEASE
. This is a mandatory requirement for Kyndryl Modern Operations Applications to be able to commit request forms to this repository.
GitHub repository for GitOps content and submitted orders not yet approved repository:
Create a branch called
Orders
. This is a mandatory requirement for Kyndryl Modern Operations Applications to commit order tracking folders to the GitHub repository for approved orders. You will also be able to commit your own manually created order templates to this repository to kick off orders without navigating to Kyndryl Modern Operations Applications. Do not delete anything on this branch because doing so will impact the ability to trace previous orders placed using GitOps.

usage: ./setup_gitops_adapter.sh [-h api-hostname] [-u username] [-p apikey]"
-h (Required): Enterprise Marketplace API url. tenant API gateway url
-u (Required): userid. userid to be used to connect with your Enterprise Marketplace tenant
-p (Required): apikey. apikey required to connect with Enterprise Marketplace tenant

Navigate to the
Provider Account
page. To learn more about navigating to the different services from each tenant, refer to Landing page navigation or Kyndryl Bridge Landing page navigation.
The page displays a list of the accounts created. Click the
Asset Accounts
tab and then click
New Asset Account
.
On the
New Asset Account
page, select
GitOps
.
Enter a
Name
and an optional
Description
for your account.
In the
Endpoint URL
field, enter your GitHub’s repository username URL, such as
https://[your enterprise domain]/api/v3/repos/[username]
. For standard GitHub, this would be
https://api.github.com/repos/[organizationname]
.
Keep the
Status
as
Active
.
Click
Create Account
.

curl --request GET 'https://mcmp-emp-pdm-demo-api.multicloud-ibm.com/adapter/webhooklisteners' \
--header 'apikey: <apikey that is obtained from the Developer Console => API key . We can find the developer console on the right>' \
--header 'username: <userid that we get from the tenant instance by clicking on the profile icon on to the right side>' \
--header 'Content-Type: application/json' \
ample generated webhook url

{
 "providerCode": "git",
 "mcmpwebhooktoken": "5f24f7bf-5222-4fe1-8e7d-99eef878e640",
 "url": "https://mcmp-emp-pdm-demo-api.multicloud-ibm.com/adapter/webhooks/git"
}

RSA public and private key pair
AES256 data key

Navigate to the
Developer Console
. To learn more about navigating to the different services from each tenant, refer to Landing page navigation or Kyndryl Bridge Landing page navigation.
In the Application field, select
consume
.
In the Service field, select
GitOps_API
.
In the
Key Request API
section, select the POST API.
Click
Try it out
.
In the
keys request body
section, substitute the
“string”
text with your preferred passphrase.
Click
Execute
.

curl --location --request POST 'https://mcmp-emp-pdm-demo-api.multicloud-ibm.com/adapter/encryption/generateKeys' \
--header 'apikey: <apikey that is obtained from the Developer Console => API key . We can find the developer console on the right>' \
--header 'username: <userid that we get from the tenant instance by clicking on the profile icon on to the right side>' \
--header 'Content-Type: application/json' \
--data-raw '{
   "password": "<passphrase>"
}'

Parse the request form to get the encrypted information, the encrypted AES256 data key, and the encrypted initialization vector used for the AES256 data key.
Decrypt the AES256 data key encrypted with the public key using the private key.
Decrypt the encrypted information received in the request form using the AES256 data key.

#!/bin/bash
echo "this script is tested on rhel 8 and ubuntu 20.04"

encryptedCredentials="$ENCRYPTED_CREDS"
ecryptedAESDataKey="$ENCRYPTED_DATA_KEY"
ecryptedIV="$ENCRYPTED_IV"
privatekeyfilepath="$PRIVATE_KEY_FILEPATH"

openssl rsa -in $privatekeyfilepath -out decryptedprivatekey.pem

#decrpyt  datakey using privatekey
echo -n $ecryptedAESDataKey | base64 --decode | openssl rsautl -decrypt -inkey decryptedprivatekey.pem -out datakey.json -keyform PEM -oaep
decryteddatakey=$( jq '.data'  datakey.json )

#decrpyt  IV using privatekey
echo -n $ecryptedIV | base64 --decode | openssl rsautl -decrypt -inkey decryptedprivatekey.pem -out iv.json  -keyform PEM -oaep
decrytediv=$( jq '.data'  iv.json )

convert_buffer_to_hex() {
buffer=$1
spaced_array=$(echo "$buffer" | tr , " ")
final_array=$(echo "$spaced_array" | tr [] " ")

# Variable to hold hex value
hex=""

for ss in $final_array; do
hex="$hex$(printf "%02x" "$ss")"
done

echo "$hex"
}

#converting datakey to hex
hexedkey=$(convert_buffer_to_hex "$decryteddatakey")
echo "$hexedkey"

#converting iv to hex
hexediv=$(convert_buffer_to_hex "$decrytediv")
echo "$hexediv"

# decrypt credentials using key and iv
echo $encryptedCredentials | base64 -d | openssl enc -aes-256-cbc -A -d -p -out credentials.txt -K $hexedkey -iv $hexediv -nosalt -nopad

#encrypted credentials value received in the Request Form
export ENCRYPTED_CREDS=""

#encrypted data key received in the Request Form
export ENCRYPTED_DATA_KEY=""

#encrypted Initialization Vector value received in the Request Form
export ENCRYPTED_IV=""

#absolute filepath where private key is located on the system
export PRIVATE_KEY_FILEPATH=""

`sh decryption.sh`

$ ./decryption.sh

Enter pass phrase for ./private.pem:
writing RSA key
249c6022e2bc32c6b755c72147740d017fe1xxxxxxxxxxxxxxxxxxxxxxxxx
key=249C6022E2BC32C6====================================================
iv =9DD301D2DBxxxxxxxxxxxxxxxxxxx

`cat credentials.txt`