Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Project specific environments #1767

Merged
merged 1 commit into from
Jun 28, 2021
Merged

Conversation

iLLiCiTiT
Copy link
Member

@iLLiCiTiT iLLiCiTiT commented Jun 25, 2021

Issue

Applying of project specific environments was broken as it didn't update environments but set it again which was unexpected for launching from launcher and ftrack.

Current state of project specific environments is that it will break all environments if it's not empty.

Changes

  • fix project specific environment variables to work as expected with updating the value instead of setting the value back

How to test

  • I did it with adding custom environment in application envirtonments ("MY_TEST_ENV": "VALUE_1")
    image

  • In project settings I've added "MY_TEST_ENV": "{MY_TEST_ENV} - VALUE_2"
    image

  • On application launch checked if OpenPype loaded and if value of env "MY_TEST_ENV" is "VALUE_1 - VALUE_2"
    image

@iLLiCiTiT iLLiCiTiT self-assigned this Jun 25, 2021
@iLLiCiTiT iLLiCiTiT added backend type: bug Something isn't working labels Jun 25, 2021
@iLLiCiTiT iLLiCiTiT added the HIGH label Jun 25, 2021
@iLLiCiTiT iLLiCiTiT merged commit 450892c into develop Jun 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants