Defang compose up showing Error: missing configs:"API_KEY"

[acote88]

"I don't know is whether that's a Defang api key, an AWS api key, or something else. Why do I need an API key? I'm just following your tutorial. Shouldn't I have been prompted to set one up?"

[lionello]

We do show a hint when the compose up fails due to an issue with secrets

[lionello]

After generate we can detect whether the project was generated with secrets and immediately prompt the user to add the secret? Alternatively we can add to the prompt to not use any secrets, but that severely limits code generation.

[yuta519]

@acote88
If it's possible, you can try to generate and run compose up on another directory again.
Although I also faced the same problem at first, I could finally solve the problem by changing the directory where I run the command.

This is the log when I first run the command.

$ defang generate
 * Connecting to fabric-prod1.defang.dev:443
? Please describe the service you'd like to build: Hello World
? What folder would you like to create the service in? service1
 * Working on it. This may take 1 or 2 minutes...
 * Writing files to disk...
   - docker-compose.yml
   - Dockerfile
   - package.json
   - main.js
 * Code generated successfully in folder service1

Check the files in your favorite editor.
To deploy the service, `cd service1` and do:

  defang compose up

A newer version of the CLI is available at https://github.com/defang-io/defang/releases/latest
*

$ defang compose up                                      
 * Connecting to fabric-prod1.defang.dev:443
WARNING ingress port without healthcheck defaults to GET / HTTP/1.1 
WARNING missing memory reservation; specify deploy.resources.reservations.memory to avoid out-of-memory errors 
 * Compressing build context for service1 at /Users/yuta519/work/service1
 * Uploading build context for service1
 * Deploying service service1
Error: failed_precondition: missing secret source:"API_KEY"

To manage service secrets, use:

  defang secret

On the docker-compose.yml which was automatically generated included API_KEY:

version: '3.9'
services:
  service1:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - mode: ingress
        target: 3000
    secrets:
      - API_KEY
secrets:
  API_KEY:
    external: true

When I changed the directory , this yml was different like the below.

version: '3.9'
services:
  service1:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - mode: ingress
        target: 3000
#secrets:
  #API_KEY:
    #external: true

Also, I tried to set a secret, however, I'm not sure yet.

$ defang secret ls 
 * Connecting to fabric-prod1.defang.dev:443
{}
A newer version of the CLI is available at https://github.com/defang-io/defang/releases/latest

$ defang secret set        
 * Connecting to fabric-prod1.defang.dev:443
Error: required flag(s) "name" not set

$ defang secret set API_KEY
Error: unknown command "API_KEY" for "defang secret set"

To manage service secrets, use:

  defang secret

[lionello]

Need better DX after generating/instantiating a project that requires config. CLI shows defang compose up which results in the error; should show defang config set … instead.