You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
amarjandu opened this issue
Jan 5, 2021
· 1 comment
Labels
debt[type] A defect incurring continued engineering costenh[type] New feature or requestinfra[subject] Project infrastructure like CI/CD, build and deployment scriptsorange[process] Done by the Azul teamspike:3[process] Spike estimate of three points
There might be a way to utilize the parent env functionality in scripts/export_environment.py to allow for a personal deployment to derive the majority of its values from deployments/sandbox/environment.py file.
This could be done by:
setting the directory name for a personal deployment to sandbox.foo
add personal changes to the deployment/foo/environment.py file
add personal local changes to the deployment/foo/environment.local.py file
We should spike to see if this is possible.
The text was updated successfully, but these errors were encountered:
This would use the existing mechanism added for dev.gitlab and prod.gitlab.
melainalegaspi
added
spike:3
[process] Spike estimate of three points
enh
[type] New feature or request
infra
[subject] Project infrastructure like CI/CD, build and deployment scripts
labels
Jan 6, 2021
theathorn
added
debt
[type] A defect incurring continued engineering cost
and removed
enh
[type] New feature or request
labels
Jan 25, 2021
debt[type] A defect incurring continued engineering costenh[type] New feature or requestinfra[subject] Project infrastructure like CI/CD, build and deployment scriptsorange[process] Done by the Azul teamspike:3[process] Spike estimate of three points
There might be a way to utilize the parent env functionality in
scripts/export_environment.py
to allow for a personal deployment to derive the majority of its values fromdeployments/sandbox/environment.py
file.This could be done by:
sandbox.foo
deployment/foo/environment.py
filedeployment/foo/environment.local.py
fileWe should spike to see if this is possible.
The text was updated successfully, but these errors were encountered: