Running Shotgrid services live

[jberkheimer]

I posted this on the Discord chat originally but now I am putting this on the forum for a broader discussion and clarification on this topic.

---

Can anyone tell me what happened to the credential info in the Shotgun addon settings?

@antirotor responded:

It is using Secrets now, change made here Chore: Remove unused local Flow authentication. by rdelillo · Pull Request #194 · ynput/ayon-shotgrid · GitHub

---

My response was for more clarification:

OK can you help me out with this a bit. So if I am reading this right, I need to set this in our local ayon-shotgrid repo?

I have yet to test this as I am still running the older version of the Shotgrid servers. I am in the process of building a new server off of the latest code. The issue seems like the older version got the credentials from the Ayon server from the Addon settings.

To provide further context, we run these Shotgrid services in a Coreweave Kubernetes pod. So I’m wondering if I need to add our credentials to the pod sealed-secrets.json. We are doing something similar for out Ayon credentials.

[mustafa_jafar]

So, are you running your shotgrid services outside of AYON services management page?
If yes, then you always need to use a matching service version. typically the mentioned versions in the package.py.

On the other hand, you can run the services locally live from code.
as an example, you can follow my shotgrid services commmands. e.g.

.vscode/tasks.json

[jberkheimer]

@mustafa_jafar

So, are you running your shotgrid services outside of AYON services management page?
If yes, then you always need to use a matching service version. typically the mentioned versions in the package.py.

I’m pretty sure the answer to this is yes. We are still running the setup that Fabia established over a year ago. It’s running in our Coreweave instance via Kubernetes. I have not touched this setup much because it worked.

While doing some dev work in the services I did have them running locally, so I’m familiar with that. I just wasn’t sure how the new .env file played into this. I’m assuming our older version got the credentials from the Ayon database. But since they aren’t kept there any longer I have to set them in the .env files?

[mustafa_jafar]

@jberkheimer

I have not touched this setup much because it worked.

I feel you. I hope you find away around it.
It’s also pretty interesting that your service didn’t complain about the addon version.
I recall when running services with version that doesn’t match my addon version, it fails to get the addon settings.

@jberkheimer

I’m assuming our older version got the credentials from the Ayon database.

I believe it mostly got it from the settings.

[jberkheimer]

Hey @mustafa_jafar I was offline with COVID since last week. But I’m slowly getting back to work. I decided that I’m going to rework our deployment strategy a bit so I will be making some changes to how we deploy the Shotgrid services. I’ll try to document my progress and keep you guys in the loop so you can get a sense of what I’m doing.

I do want to add that I had missed this section in the Shotgrid addon settings. So hopefully this clears up some of my confusion over the credentials.