Have something to say?

Tell Qovery how they could make the product more useful to you.

πŸ”™ In Product Backlog

Built-in Qovery Docker with qovery CLI installed

Currently to create a lifecycle job, the only option is to use Docker mode where you specify a Dockerfile. With this in mind if I have a script that use the Qovery CLI the only option I see available is either have a Dockerfile that installs the CLI or use FROM ghcr.io/qovery/qovery-cli:latestIt would be great if there was a builtin Docker image to choose from that has the qovery CLI installed, so the process is faster and no need to build it, that way we could just run a script like#!/bin/sh set -e qovery application domain create -n "app" --domain api.preview-$QOVERY_PULL_REQUEST_ID-domain.com and only configure the CMD arguments to run the bash script like ["script.sh"] in the Qovery Console.

Moises Alejandro 25 days ago

πŸ”™ In Product Backlog

[Terraform provider] - Use a special resource for deployment stage order and clean

For simplest resources using is_before and is_after is sufficient when we create a qovery_deployment_stage resource. But when you want to rationalise and automatise the creation of the qovery environment with modules and list of stages to create, things are not smooth. You can't create a qovery_deployment_stage resource in a for loop and generate is_previous or in_after in same resource. Have a qovery_deployment_stage_order could dissociate the creation of the stage and his order. Furthermore, when we create a qovery_deployment_stage it simply add it on already existent default stages. Have a clean_default boolean into qovery_deployment_stage or a resource to control these would be a nice to have.

MickaΓ«l G. 2 months ago