Partner Workflow
1. Introduction
This tutorial is for Partners. You will learn how to connect your own Git repository, publish private modules, deploy and test them, retrieve deployment outputs, and use the Jules AI assistant to refine your modules.
2. Step 1: Connect GitHub
- Click your Profile Avatar -> Profile.
- Scroll to Partner Settings.
- Enter your GitHub Access Token (ensure it has
reposcope). - Click the Fetch Repos button.
- Select your Repository from the dropdown list that appears.
- Click Save Github Settings.
Multiple repositories: You can connect more than one repository. Repeat the steps above for each additional repository — each saved token/repo pair is stored separately, and modules from all connected repositories appear on the Publish page.
3. Step 2: Configure Jules (Optional)
Jules is an AI assistant that can help you analyse and improve your Terraform modules directly within the platform.
- In the same Partner Settings section, scroll to API Settings.
- Enter your Jules API Key.
- Click Save API Settings.
Once configured, the Jules sparkle icon (✨) will appear on module cards in the Publish page.
Using Jules to Refine a Module
- Navigate to Publish.
- Find the module you want to improve and click the Sparkles Icon (✨).
- A Jules session panel opens scoped to that module. You can:
- Ask Jules to explain what the module does or review its structure.
- Describe an issue a user reported and ask Jules to suggest a fix.
- Request that Jules propose improvements to variable names, descriptions, defaults, or module logic.
- Attach additional context using Add Source (e.g., paste a log snippet or a second Terraform file).
- Review Jules's suggestions in the Activities list.
- Click Approve on any suggestion you want to apply, or dismiss ones that don't apply.
- After applying improvements, return to the Publish page and click Update to push the refreshed module definition to the platform.
4. Step 3: Publish a Module
- Click Publish in the navigation bar.
- The page will scan your connected repositories and list valid modules.
- Find the module you want to share (e.g.,
my-custom-app). - Click the module card to select it.
- Click the Publish (or Update) button.
- Success! You are redirected to the Deploy page.
Module visibility: By default, a newly published Partner Module is visible only to you and platform Administrators. To grant access to specific users, contact your platform administrator.
5. Step 4: Deploy and Test Your Module
- On the Deploy page, the Partner Modules tab is shown first by default. It lists only the modules you have published from your own repository.
- You should see
my-custom-applisted there. To deploy platform modules or partner modules from other publishers, click the Platform Modules tab. - Click the module card, configure the variables, and deploy it just like a standard module.
- Partner exemption: When you deploy a module you own, the credit cost is always zero — no credits are deducted from your balance regardless of the module's defined
credit_cost. You are also exempt from the credit purchase restriction, meaning you can deploy any module regardless of your Purchased Credits balance.
Viewing Deployment Outputs
After a successful deployment, the Terraform outputs from your module are available in the platform UI:
- Navigate to Deployments and click the Deployment ID of your module's deployment.
- Click the Outputs tab.
- You will see all values exported by your module's
outputs.tf— URLs, IP addresses, service endpoints, generated resource names, etc. - These outputs are also the values that your end users will see after deploying your module. Verify that all expected outputs are present and correctly named before sharing the module broadly.
Tip: If an output is missing, check that it is defined in
outputs.tfand thatterraform applycompleted without errors. Partial apply failures can result in some outputs being unavailable.
6. Step 5: Contact a Module Publisher
If you need to reach the publisher of a platform module (for example, to report an issue or request a feature):
- Navigate to Deploy and open the module card.
- Click Contact Publisher (if the option is available for that module).
- Fill in your message and submit. The message is routed to the module's registered owner.