philibea / scaleway-containers-deploy Goto Github PK

Hi,

First of all, thank you for your work.

I just noticed that at the end of a deployment, all the environment variables present on Scaleway are leaked in the Github Action logs. Is it possible to hide this?

My conf :

      - name: StepName
        id: deploy
        uses: philibea/[email protected]
        with:
          type: deploy
          scw_access_key: ${{ secrets.SCW_ACCESS_KEY }}
          scw_secret_key: ${{ secrets.SCW_SECRET_KEY }}
          scw_containers_namespace_id: ${{ secrets.SCW_CONTAINERS_NAMESPACE_ID }}
          scw_registry: rg.fr-par.scw.cloud/xxxx/yyyy:staging
          scw_container_port: 3333

Example of leak in action logs :

waiting for namespace to be ready
Container Name:  staging
Container already exists and will be updated &{xxxx staging *** ready map[APP_KEY:xxxxCACHE_VIEWS:false DB_CONNECTION:mysql DRIVE_DISK:s3 HASH_DRIVER:bcrypt HOST:0.0.0.0 ....

Am i missing something or cant you set the name of the container manually?

Hi,
we are looking into vercel-style preview deployments on scaleway and it would be really cool to be able to configure some more scaling options through this action, particularly useful would be

• min and max instance count
• cpu
• concurrent connections

would it be possible to make those configurable?

Hi i have tried adding environment variables to the github action but they dont show up in scaleway. Its the same for the secret environment variables

Example
scw_environment_variables: SOMEVARIABLE1=1234,SOMEVARIABLE2=12345

Github actions also show this warning (also for the secrets if they are added)
Unexpected input(s) 'scw_region', 'scw_environment_variables', valid inputs are ['entryPoint', 'args', 'type', 'scw_access_key', 'scw_secret_key', 'scw_containers_namespace_id', 'scw_registry', 'scw_container_port', 'scw_dns', 'scw_dns_prefix']