Apollo GraphOS

What a member can do

• Search and read Apollo's documentation and the Apollo Connectors specification.
• Read a graph variant's details, launches and launch history.
• Read operation, subgraph and client traffic metrics.
• Run schema checks and lint checks, and validate client operations against a published schema.
• Read a subgraph schema, and publish or delete a subgraph, which triggers composition.

Each task names the Apollo GraphOS tools it may call. apollo-graphos on a task means every tool the Apollo GraphOS server offers; a name such as apollo-graphos.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A Apollo GraphOS connection acts as the Apollo GraphOS account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect Apollo GraphOS for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on Apollo GraphOS waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a Apollo GraphOS tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Connect it

Apollo GraphOS is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find Apollo GraphOS and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. Apollo GraphOS's sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and Apollo GraphOS shows as connected.
5. Name the tools on the task, apollo-graphos for all of them or each by name.
6. Check it. Run a task that reads something from Apollo GraphOS. The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your Apollo GraphOS account.

A first task to try

With Apollo GraphOS connected, give a member a task that uses it. For example:

Before each release, run schema checks on our graph and report any breaking change with the operations it affects.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the Apollo GraphOS tools it may use and its instructions. Nothing is created until you approve it.