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

chore(ci): deprecate deployment configs #1123

Open
DerekRoberts opened this issue Aug 27, 2024 · 3 comments
Open

chore(ci): deprecate deployment configs #1123

DerekRoberts opened this issue Aug 27, 2024 · 3 comments
Assignees
Labels
dependencies Pull requests that update a dependency file

Comments

@DerekRoberts
Copy link
Member

No description provided.

@DerekRoberts DerekRoberts added the enhancement New feature or request label Aug 27, 2024
@DerekRoberts DerekRoberts self-assigned this Aug 27, 2024
@DerekRoberts DerekRoberts added dependencies Pull requests that update a dependency file and removed enhancement New feature or request labels Aug 27, 2024
@paulushcgcj
Copy link
Collaborator

Feel free to start whenever you're ready

@paulushcgcj
Copy link
Collaborator

This change is feature complete, but this PR will be closed to free resources in dev. Also, due to the proximity to the new feature release, we decided to park it to avoid someone merging it.

The branch will still exist and this PR will be reopened. As of today, there's still uncertainty regarding the change from deploymentConfig to deployment as we can't afford to lose the data inside the Postgres database, and we need to be very careful when doing any kind of breaking change in production.

Thank you @DerekRoberts for the work, we will resume it as soon as we are done with this feature.

@paulushcgcj
Copy link
Collaborator

This issue will remain open as a reference to the pull request and branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants