Configuring the Production Stream Instance

Now we're going to do the same steps in the production environment that we did in the development environment.

Configure the Prod Stream Instance

1. Click the Stream Prod top tab.

2. In Stream’s own top nav, at the far right, click the AA button to open the Account menu.

3. Click Global Settings on this menu.

4. This opens Stream's Global Settings sidebar, with the focus on General Settings. Click Git Settings, a few links further down the same sidebar.

5. On the nested Git Settings nav bar, click the Remote tab.

6. In the Remote URL field, enter or paste same the string you earlier copied from the remote repo and pasted into this field in the dev instance. If you used the default naming, this will be:

   git@gitops-gitea:gituser/stream-config.git

   (If you named your Gitea repo something other than stream-config, then modify the <reponame>.git substring of the above URL to match your repo name.)

7. Stream's Authentication type drop-down defaults to SSH, which is the transport we want. Copy and paste the following key into the SSH private key field:

   -----BEGIN OPENSSH PRIVATE KEY-----
   b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAaAAAABNlY2RzYS
   1zaGEyLW5pc3RwMjU2AAAACG5pc3RwMjU2AAAAQQREL+oz/hLb4W8/TA7dQR7em4F6G1RU
   3NhujQOjHe2zVUZapKhEdOxmqO3av5ehGOVMyAYmmhosOPkpHTwGCCc0AAAAsGHLF+hhyx
   foAAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEQv6jP+Etvhbz9M
   Dt1BHt6bgXobVFTc2G6NA6Md7bNVRlqkqER07Gao7dq/l6EY5UzIBiaaGiw4+SkdPAYIJz
   QAAAAgSo+UVX4HKkk4XZP39rDcCNEuVpz4teuEqR03dDkGFTwAAAAYc2FuZGJveCtnaXR1
   c2VyQGNyaWJsLmlv
   -----END OPENSSH PRIVATE KEY-----

8. Set the SSH strict host key checking toggle to No. As earlier on the dev instance, this will allow your first push to the remote repo to accept the host key information.

9. Click Save, and look for a green confirmation message.
   NOTE: If you see an error about strict key checking here, make sure you complete the following steps. Stream checks the key prior to a push, and can throw errors if strict checking is not re-enabled.

10. Set the SSH strict host key checking toggle back to Yes. After the first save, Stream checked the SSH key; now we need to re-enable strict checking before we can actually push.

11. Click Save again.

Reminder: Best Practice - Git Security

As we saw for the development branch – and reiterated just above – it's a best practice to toggle SSH strict host key checking back to Yes after you've established the SSH transport.

Now we're almost ready to put the production Stream instance under GitOps workflow control. En route, we'll commit the config changes we just made, so that they aren't lost on restart. Stay on the Stream Prod top tab for these next steps:

Enabling GitOps Workflow

1. In this Stream instance's top nav, click the Version Control () button, and from the Version Control fly-out, click Commit.
2. In the resulting Git Changes – Global dialog, enter a commit message (e.g., Added prod remote config).
3. Click Commit Only.

Now, let's get into our Push workflow.

1. In Git Settings, click the nested General tab.
2. From the Branch drop-down, select prod.
3. Click Save.
4. In the resulting confirmation dialog, click Yes. (This will restart Stream to enable the new branch connection.)
5. After Stream restarts, set the GitOps Workflow drop-down to Push .
6. Again click Save.

After you've completed this last step, you should see a green confirmation message, and a red banner like this at the top of the production Stream instance's UI:

This banner warns us that this Stream instance's configuration is now entirely dependent on push commands from its remote repo. The message also us how to restore the instance's independent workflow.

Before we can proceed to working with GitOps, we need to do one more Git operation, to record the workflow change.

Commit the Workflow Change

1. In Stream's top nav, again click the Version Control button (), and from the Version Control fly-out, click Commit.
2. In the resulting Git Changes – Global dialog, enter a commit message (e.g., Switched to GitOps Push workflow).
3. Click Commit and Push.
4. Look for a green confirmation message.

Now we're ready to do some GitOps.