Conversation
…tings, billing details - clusters: document the cluster Deployments tab (history + per-deployment logs, "Dry run" badge) and AWS quota warnings on cluster status - blueprints: document the "Blueprint configuration" settings page for reconfiguring an existing blueprint service - organization: note the required billing details (address, VAT for EU) at organization creation / when adding a card Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
qovery-doc-mintlify-proxy | 5de29da | Sep 24 2026, 03:02 PM |
Agent tasks now let you pick the model the agent runs on. Once a provider token is selected, a Model dropdown lists the models available to that token (for AWS Bedrock, filtered by the token's AWS region); the first is selected by default, and the choice can be changed later from Settings > AI configuration. Source: Qovery/console#3005 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jul-dan
marked this pull request as ready for review
September 25, 2026 13:37
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
3 issues found across 4 files
Confidence score: 4/5
docs/configuration/clusters.mdxcould mislead readers into thinking a visible status label changes; describe the Quota issue tooltip instead.docs/configuration/agent-tasks/overview.mdxrenames a step while four other docs still use its old name, leaving labels inconsistent; update those references.docs/configuration/blueprints.mdxsays users can edit variables despite stating that context variables are read-only; clarify which variables can be edited.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/configuration/agent-tasks/overview.mdx">
<violation number="1" location="docs/configuration/agent-tasks/overview.mdx:27">
P3: Renaming this step leaves four other docs pointing at the old name. Update them so the labels match the new step title.</violation>
</file>
<file name="docs/configuration/clusters.mdx">
<violation number="1" location="docs/configuration/clusters.mdx:169">
P2: This describes a changed status label, but the feature is a **Quota issue** tooltip on services. Describe the tooltip rather than implying the visible indicator label changes.</violation>
</file>
<file name="docs/configuration/blueprints.mdx">
<violation number="1" location="docs/configuration/blueprints.mdx:201">
P3: This new paragraph says users can "review and edit the variables" on the Blueprint configuration page, but the same page states earlier that context variables (like `region` and `cluster_name`) are read-only and cannot be edited. Clarify that only the blueprint's editable variables and overridable engine settings can be changed, so the section doesn't contradict the reference table.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| - a **message** describing the issue, | ||
| - a **suggested action** — typically requesting an AWS quota increase, then retrying or waiting for the cluster to scale again. | ||
|
|
||
| While the warning is active, the cluster-status indicator shown next to your services (on the service overview) reads **Quota issue** instead of the generic warning label. The warning clears automatically once new nodes can be scheduled again; it may remain visible for a short time after the last occurrence. |
Contributor
There was a problem hiding this comment.
P2: This describes a changed status label, but the feature is a Quota issue tooltip on services. Describe the tooltip rather than implying the visible indicator label changes.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/configuration/clusters.mdx, line 169:
<comment>This describes a changed status label, but the feature is a **Quota issue** tooltip on services. Describe the tooltip rather than implying the visible indicator label changes.</comment>
<file context>
@@ -157,6 +157,17 @@ Qovery tracks cluster health using two status categories:
+- a **message** describing the issue,
+- a **suggested action** — typically requesting an AWS quota increase, then retrying or waiting for the cluster to scale again.
+
+While the warning is active, the cluster-status indicator shown next to your services (on the service overview) reads **Quota issue** instead of the generic warning label. The warning clears automatically once new nodes can be scheduled again; it may remain visible for a short time after the last occurrence.
+
### Performing Actions on Clusters
</file context>
Suggested change
| While the warning is active, the cluster-status indicator shown next to your services (on the service overview) reads **Quota issue** instead of the generic warning label. The warning clears automatically once new nodes can be scheduled again; it may remain visible for a short time after the last occurrence. | |
| While the warning is active, affected services show a **Quota issue** tooltip next to the cluster-status indicator. The warning clears automatically once new nodes can be scheduled again; it may remain visible for a short time after the last occurrence. |
| Connect a Qovery service, a Git repository, or both, for the agent to load as context. A Qovery service's linked Git repository is included automatically, no need to add it separately, connect a repository on its own only when it isn't tied to a Qovery service. | ||
| </Step> | ||
| <Step title="Choose a Provider"> | ||
| <Step title="Choose a Provider and Model"> |
Contributor
There was a problem hiding this comment.
P3: Renaming this step leaves four other docs pointing at the old name. Update them so the labels match the new step title.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/configuration/agent-tasks/overview.mdx, line 27:
<comment>Renaming this step leaves four other docs pointing at the old name. Update them so the labels match the new step title.</comment>
<file context>
@@ -24,8 +24,10 @@ Agent Tasks are one-time or scheduled jobs delegated to AI agents, running on yo
Connect a Qovery service, a Git repository, or both, for the agent to load as context. A Qovery service's linked Git repository is included automatically, no need to add it separately, connect a repository on its own only when it isn't tied to a Qovery service.
</Step>
- <Step title="Choose a Provider">
+ <Step title="Choose a Provider and Model">
Pick **Claude** (Anthropic) or **AWS Bedrock**, then select an existing token or create a new one on the fly. A token created here is saved and can be reused by any other agent task in the organization, no need to re-enter credentials each time. Tokens can also be managed centrally from **Organization Settings > Agent > Token**.
+
</file context>
|
|
||
| ## Editing a Blueprint Service | ||
|
|
||
| After a blueprint service is created, you can change the inputs it was provisioned with from its **Blueprint configuration** settings page. Open the blueprint service, go to its **Settings**, and select **Blueprint configuration** to review and edit the variables and any overridable engine settings the blueprint exposes (see [Variables & Engine Reference](#variables--engine-reference)). Secret values are handled without exposing the stored secret, and the **Overrides** section is collapsed by default. |
Contributor
There was a problem hiding this comment.
P3: This new paragraph says users can "review and edit the variables" on the Blueprint configuration page, but the same page states earlier that context variables (like region and cluster_name) are read-only and cannot be edited. Clarify that only the blueprint's editable variables and overridable engine settings can be changed, so the section doesn't contradict the reference table.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/configuration/blueprints.mdx, line 201:
<comment>This new paragraph says users can "review and edit the variables" on the Blueprint configuration page, but the same page states earlier that context variables (like `region` and `cluster_name`) are read-only and cannot be edited. Clarify that only the blueprint's editable variables and overridable engine settings can be changed, so the section doesn't contradict the reference table.</comment>
<file context>
@@ -196,6 +196,16 @@ The engine block defines how the resource is provisioned. Which settings you can
+## Editing a Blueprint Service
+
+After a blueprint service is created, you can change the inputs it was provisioned with from its **Blueprint configuration** settings page. Open the blueprint service, go to its **Settings**, and select **Blueprint configuration** to review and edit the variables and any overridable engine settings the blueprint exposes (see [Variables & Engine Reference](#variables--engine-reference)). Secret values are handled without exposing the stored secret, and the **Overrides** section is collapsed by default.
+
+Save your changes, then redeploy the service to apply them.
</file context>
Suggested change
| After a blueprint service is created, you can change the inputs it was provisioned with from its **Blueprint configuration** settings page. Open the blueprint service, go to its **Settings**, and select **Blueprint configuration** to review and edit the variables and any overridable engine settings the blueprint exposes (see [Variables & Engine Reference](#variables--engine-reference)). Secret values are handled without exposing the stored secret, and the **Overrides** section is collapsed by default. | |
| After a blueprint service is created, you can change the inputs it was provisioned with from its **Blueprint configuration** settings page. Open the blueprint service, go to its **Settings**, and select **Blueprint configuration** to review and edit the blueprint's editable variables (read-only context variables stay locked) and any overridable engine settings the blueprint exposes (see [Variables & Engine Reference](#variables--engine-reference)). Secret values are handled without exposing the stored secret, and the **Overrides** section is collapsed by default. |
TheoGrandin74
approved these changes
Sep 25, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents user-facing changes merged into
qovery/consolemainduring the analysis window (first-run fallback, last 14 days).This supersedes the closed PR #198 and addresses the review feedback left on it:
Changes already covered by recent PRs — AI provider tokens / AWS Bedrock (#194) and certificate renewal failure alerts (#195), and the Agent Tasks Outputs concept already in
configuration/agent-tasks/— are intentionally not duplicated.Documented changes
1. Cluster Deployments (history, logs, dry-run badge)
The cluster Deployments tab lists a cluster's past deployments (status, timestamp, duration, trigger), with per-deployment logs; dry-run deployments show a Dry run badge. Now available by default (feature flag removed).
configuration/clusters.mdx(new "Deployments" section)2. AWS quota warnings on clusters
When an AWS service quota is reached and Karpenter can no longer create nodes, the cluster status becomes Warning with a callout on the cluster overview (quota name or code, impacted resource, message, suggested action), and services on that cluster show a Quota issue status tooltip.
configuration/clusters.mdx(new "AWS Quota Warnings" subsection under Statuses)3. Blueprint configuration settings page
Blueprint-backed services now have a dedicated Blueprint configuration settings page to review and edit the variables and overridable engine settings after creation.
configuration/blueprints.mdx(new "Editing a Blueprint Service" section)4. Billing details validation
Creating an organization / adding a payment card now requires a complete billing address, a VAT number for EU billing countries (optional elsewhere), and validates supported postal-code formats per country.
configuration/organization.mdx(Billing section)5. Agent task model selection
When creating or editing an agent task, once a provider token is selected a Model dropdown lists the models available to that token (for AWS Bedrock, filtered by the token's AWS region). The first available model is selected by default, and the choice can be changed later from the agent task's Settings > AI configuration.
configuration/agent-tasks/overview.mdx("Choose a Provider and Model" step)Skipped as not user-facing / already documented
configuration/agent-tasks/.Run-state note
DOCS_AGENT_LAST_RUN_ATdid not exist at the start of this run (confirmed via the Qovery MCP), so this run used the 14-day first-run fallback window (since2026-09-11T08:00:56Z). The window's user-facing Console changes were re-verified against source; no documentable change merged since PR #198/#199 was first opened. On success, the variable is created with this run's start time2026-09-25T08:00:56Zso the next run analyzes only newer commits.Generated by the documentation update agent.