DevOps Community Sponsored by Cloud Posse

SweetOps

I see that `pkg/auth/integrations/github/sts.go` is locked to Atmos Pro. I have been using (self-hosted) version of <https://github.com/octo-sts/app|ChainGuard's >`octo-sts` for the past year. Is this something want to keep locked Atmos Pro?

Let me know if I should move conversation to <#C031919U8A0> . I can also submit feature request on the repo. Ill do the PR if `octo-sts` support is allowed to be added.

If GitHub STS is locked to Atmos Pro, I completely understand.

I'm not directly opposed to it, other than I the Atmos Pro version is not identical to ChainGuard's.

Try Atmos Pro? :rolling_on_the_floor_laughing:

&gt; Try Atmos Pro?
It's still on my list. Probably late this year.

As for the Octo STS support, Ill create a PR in the future.