Tasking Manager API - Frontend previous version. #369
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ge stats on tasking manager.
…evelop and our iD fork. Needs testing.
…-env-variables Update a number of env variables.
…rbo-deploy Release v2.0.4 (translation updates) of overpass-turbo.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are many changes in this PR, but all are related to TM, including the migration and software upgrade. The iD editor is not working properly in the latest version of TM, so for now, we will continue using/offering the previous version of TM. I have reverted all the changes I made for the migration and upgrade. The changes we made for upgrading TM can be found here: https://github.com/OpenHistoricalMap/ohm-deploy/tree/tm-fix-version
In addition to reverting those changes, I also fixed the Helm templates, which are now set up to support both the previous and upgraded versions of TM. This will allow us to continue working on other infrastructure tasks as well.
I am also planning to create another stack in the staging cluster to test new changes in our different services - components. This will ensure that staging remains only one step behind before merging to production.
cc. @danrademacher @batpad @erictheise