Unable to run conditional action based on env variable like client.env.ENVIRONMENT

[grizzled thunder]

deploy: {
  if client.env.ENVIRONMENT != _|_ && client.env.ENVIRONMENT != "production" {
    app: core.#Nop & {
      input: _source
      }
    }

  if client.env.ENVIRONMENT != _|_ && client.env.ENVIRONMENT != "production" {
    app: core.#Nop & {
      input: _source
      }
    }
 }

if i run dagger do the deploy action is not visible, if i change client.env.ENVIRONMENT with a field i can run the action (but i need to change manually the field value)

[lone lynx]

Those 2 if blocks seems to have the same conditions in it? Is it just that logic that is flawed? Or am I missing something?

[grizzled thunder]

it is only an example and i put two equivalent block but i need to differentiate and replace core.#Nop with some real action

I need to run different action for different branch (aka environment)

[lone lynx]

Oh, I think I understand.
By having 2 conditionals, you would create 2 app that would conflict?

[surreal wind]

@grizzled thunder does client: env: ENVIRONMENT have a default value, or is it optional, in your plan by any chance? If so, you might be affected by this bug: https://github.com/dagger/dagger/issues/2680

If the answer is "yes", could you try again by removing the default value and/or making the field non-optional?

[grizzled thunder]

It can be the same issue but i found strange behaviours in general, i share a project: https://github.com/Alvise88/dagger-0.2.36-environment-issue

[haughty elm]

Hi,
It's a known issue that is not trivial to fix at all. We load env variables when loading the plan, to inject them at the start. If your env var doesn't exist, as this line covers 2 times the same state: client.env.ENVIRONMENT != _|_ && client.env.ENVIRONMENT != "production", this part of the Cue plan gets wiped from your plan

[grizzled thunder]

Ok, thank you, is there a workaround to run something similar ?