Open
Conversation
Add a detailed documentation page explaining every AWS IAM permission required by Qovery, justified by what the engine actually does with each permission. Placed under Security & Compliance and linked from the AWS installation guide.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
qovery-doc-mintlify-proxy | 613c1ec | Mar 13 2026, 02:47 PM |
lmillie-qovery
approved these changes
Mar 13, 2026
Add a detailed documentation page explaining every GCP IAM permission required by Qovery, grouped by service (GKE, Compute, Artifact Registry, Cloud Storage, Cloud Run, IAM). Placed under Security & Compliance and linked from the GCP installation guide.
Add a detailed documentation page explaining every Azure permission required by Qovery, grouped by resource provider (Container Service, Container Registry, Storage, Network, Compute, Authorization, Managed Identity, Key Vault, Insights, Features, Container Instances). Includes both control plane (Actions) and data plane (DataActions) permissions. Placed under Security & Compliance and linked from the Azure installation guide.
Add a detailed documentation page explaining every Scaleway IAM permission required by Qovery, grouped by permission set (Containers, Network Services, Compute, Storage, VPC). Covers Kapsule, Container Registry, VPC/Private Networks, Public Gateways, Load Balancers, Object Storage, Block Storage, and managed databases. Placed under Security & Compliance and linked from the Scaleway installation guide.
Add Setup Overview to AWS page, add 'What Qovery Creates in Your Account' resource inventory table to AWS, GCP, and Azure pages. All four pages now share the same structural skeleton: Setup Overview, permissions detail, resource inventory, and Security Best Practices FAQ.
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.
Add a detailed documentation page explaining every AWS IAM permission required by Qovery, justified by what the engine actually does with each permission. Placed under Security & Compliance and linked from the AWS installation guide.