Manually Stop Preview Environment in Pull Request Comment

On top of the TTL feature, it would be nice to be able to leave a comment on the Pull Request to destroy the Preview Environment (as when merged or declined). In our case we have Preview Environments created manually with the /qovery preview xxx-xxxx command. But in many cases a bug is discovered in the Preview Environment and there is no need to have the environment running because it may take hours/days to solve. Being able to have a command like /qovery preview destroy xxx-xxxx would be very helpful instead of having to close the pull request.

Moises Alejandro 1 day ago

Create Preview Environment pointing to any branch

Right now Preview Environments can only be triggered when the PR is to the branch of the service on the Blueprint environment. Example: app1 -> development, app2 -> master, app3 -> development.If I create a PR in app1 from feature -> development it will let me create a Preview Environment.If I create a PR in app1 from feature -> master it will not let me create a Preview Environment.Both cases it will have app1 with the branch feature for the Preview Environment and the rest as they are configured. It does not really matter where the PR is pointing to, the branch from where the PR was created is what it needs to be tested.

Moises Alejandro 1 day ago

A button in billing console to retry payment

Sometimes card payments fail. This blocks the deployments. Qovery automatically performs trying every 1 day. However, we would like to have a button so that we can retry the payments ourselves and enable the deployments. This is imp as sometimes there can be errors/features that needs to go ASAP

r48Bit 1 day ago

Cron Job build error should not cancel environment deployment

I have an environment that has Start & Stop enabled, and a cron job build failed, but the whole environment deployment was cancelled. A cron job build error should not cancel the whole environment.

Moises Alejandro 1 day ago

Point to branch head when cloning env (manual or automatic preview)

When cloning an environment (manually or via the preview env feature) you should decide whether the cloned env should have the branch updated to the latest commit or if it should be a pure clone of the environment used as blueprint.

Moises Alejandro 2 days ago

Jun 30

Support Mongo v7 container mode

Supporting Mongo v7 in container mode

Julien Dan 3 days ago

Lock deployments for a service

Allow to lock the deployments for a service, making it not deployable even when the deployment action is triggered on the entire environment You will still be able to trigger the deployment of the locked service alone

Alessandro Carrano 15 days ago

Jun 30

Improve deployment error troubleshoot

We will review the entire deployment log view to simplify it and ensure that you can be autonomous in solving most of the deployment errors you might face.

Alessandro Carrano 15 days ago

Jun 30

Improve build speed - share images across environments

We will review our image mirroring mechanism (https://hub.qovery.com/docs/using-qovery/deployment/image-mirroring/) to share the built images across environments if they use the same repository and commit id.This will speed up the deployment when cloning environments manually or via the preview environment feature.

Alessandro Carrano 15 days ago

Jun 30

Improve API structure

We will improve the API structure and review some legacy parts. We will at least:merge the application and container endpointsreview the cluster endpoints to better fit our current offer (managed vs self-managed)

Alessandro Carrano 15 days ago

Jun 30

Qovery Search bar

we will introduce a search bar, allowing you to quickly access some functionalities and, in the future, search for any existing resource (project, service, environment..)

Alessandro Carrano 16 days ago

1

Jun 30

Qovery Github Actions in Github Marketplace

create some github actions for the marketplace: 1: that installs and runs commands from the qovery cli, letting you specifiy the version and commands 2: one that populates a pull request page with details from qovery around the deployed solution (ie being to give the url of a deployed service)

Stephen Bennett 22 days ago

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 28 days ago

AWS - Alternative NAT Gateway

It would be great that instead of using the default AWS NAT Gateway that is quite expensive, Qovery gave us the option to choose an alternative option like https://www.cohesive.net/vns3/cloud-nat/. Where you only pay for the virtual machine runtime, not also for the data processed, as is the case with AWS's NAT Gateway.

Moises Alejandro About 2 months ago

Deploy Qovery on any existing Kubernetes cluster for demo purposes (Self-managed offer)

You will be able to deploy Qovery on a kubernetes cluster running anywhere as long as it can reach the Qovery control plane. This version will be mainly for demo purposes and it can be run locally or on any hosting provider.

Alessandro Carrano About 2 months ago

Jun 30

Intergrate CLI Shell command directly in the UI

Today you can connect to your running applications via the Shell command available in the Qovery CLI. We will add the same command directly in the Qovery console without the need to install the Qovery CLI on your computer

Alessandro Carrano About 2 months ago

[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

Using less public ipv4 on AWS

Today each EC2 started on Qovery has a public ipv4. Ipv4 started to be more expensive due to the exponential rarity. So have a way to use more ipv6 and only ipv4 as optional for specific use case. Using a centralized load balancing mechanism for inbound request (with HA for sure).

Mickaël G. 2 months ago

Customize annotations

We will allow you to customize the annotations attached to the different kubernetes objects

Alessandro Carrano 2 months ago

Jun 30

[Terraform Provider] Support deployment restrictions

We will add the deployment restriction configuration support to our terraform provider

Alessandro Carrano 3 months ago