#203 SOPs for deploying the fas2discourse operator on Fedora Infra
Merged by dkirwan. Opened by dkirwan.
dkirwan/infra-docs-fpo master  into  master

Download 203.patch

SOPs for deploying the fas2discourse operator on Fedora Infra

typo here?

So is the config baked into the image? if we want to sync a new group, how can we do that? (or remove one)

Is there any way to debug what its doing?

Should we monitor anything here?

Thanks for the doc...

So is the config baked into the image? if we want to sync a new group, how can we do that? (or remove one)

As I understand it, the current implementation does not create Discourse groups -- it syncs those that exist. So Discourse is effectively the configuration for that. (This can be done by anyone with Discourse admin. The admin also can optionally identify some group members as owners -- syncing that from sponsors is a potential future feature.)

Not sure about config for things like server name, api key, etc.

So configs are in the private ansible repo, search for fas2discourse to get a list of things such as discourse api key, few things like keytab principal etc.

Yep the way this works, it retrieves discourse groups, filters out a predetermined list of system groups which should be ignored eg the trust levels 0-4. Then queries fasjson, gets list of membership for each of these groups, then updates the discourse group membership to match what is in IPA via fasjson.

You add new groups, by creating a group in Discourse side, and as users login and create accounts on Discourse, they'll then be added to the groups which they are members of.

1 new commit added

  • typo

Let me add another SOP explaining how to interact with the Operator.

1 new commit added

  • Add SOP for interacting with the operator

And.. one more SOP for debugging issues with the Operator.

I don't see the debugging one?

rebased onto 244bf310ae80c4c243a5935b19ff720d46f8d9fb

Ah was staged but not committed! Pushed now.

Pull-Request has been merged by dkirwan

Metadata