Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use sandbox as parent for personal deployments #2667

Open
amarjandu opened this issue Jan 5, 2021 · 1 comment
Open

Use sandbox as parent for personal deployments #2667

amarjandu opened this issue Jan 5, 2021 · 1 comment
Labels
debt [type] A defect incurring continued engineering cost enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team spike:3 [process] Spike estimate of three points

Comments

@amarjandu
Copy link
Contributor

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:

  1. setting the directory name for a personal deployment to sandbox.foo
  2. add personal changes to the deployment/foo/environment.py file
  3. add personal local changes to the deployment/foo/environment.local.py file

We should spike to see if this is possible.

@amarjandu amarjandu added the orange [process] Done by the Azul team label Jan 5, 2021
@hannes-ucsc hannes-ucsc changed the title Investigate using sandbox as parent for personal deployments Use sandbox as parent for personal deployments Jan 5, 2021
@hannes-ucsc
Copy link
Member

This would use the existing mechanism added for dev.gitlab and prod.gitlab.

@melainalegaspi 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 theathorn added debt [type] A defect incurring continued engineering cost and removed enh [type] New feature or request labels Jan 25, 2021
@hannes-ucsc hannes-ucsc added the enh [type] New feature or request label Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debt [type] A defect incurring continued engineering cost enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team spike:3 [process] Spike estimate of three points
Projects
None yet
Development

No branches or pull requests

4 participants