Thread
#prefect-server
    s

    Sam Werbalowsky

    9 months ago
    I’m running into an issue after upgrading from
    0.15.4
    to
    0.15.10
    regarding Git storage - running with a kubernetes agent and deployed via helm. The storage is set using environment variables as part of our CI.
    Failed to load and execute Flow's environment: ValueError('Either `repo` or `git_clone_url_secret_name` must be provided')
    The thing is, in the UI I can see the
    repo
    value, as it is created during registration. I am assuming it isn’t getting passed to the PrefectJob pod that gets spun up, but I’m not sure why that is. Any ideas?
    I have just got the run to work by specifying the same environment variable during Run that is used to generate the Repo during the CI - Is there a way to force the job pod to use what is used during registration? I think that since the environment variable is not on the PrefectJob pod, it is passing in
    None
    rather than what is being registered.
    Anna Geller

    Anna Geller

    9 months ago
    when you use env variables for this, you need to make sure that those exist in both the registration environment and at runtime, otherwise you’ll get issues due to the mismatch of those two
    s

    Sam Werbalowsky

    9 months ago
    Makes sense - I think the update to Git storage to require Repo Name or the Secret may have masked the issue, in this case. One other thing I’m noticing is an env_var being passed as an array (single-value) rather than a string - is this something you’ve encountered before?
    Anna Geller

    Anna Geller

    9 months ago
    can you explain a bit more what do you mean?
    s

    Sam Werbalowsky

    9 months ago
    Human Error 😄
    Anna Geller

    Anna Geller

    9 months ago
    thanks for update! great you figured that out