Adding deployment ID to DB and Tier0Config #4632
Merged
Conversation
This file contains hidden or 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
9f74c3c to
bb0eb1c
Compare
bb0eb1c to
eb4c91f
Compare
Contributor
|
Hi German. I tested this PR with multiple replays and everything looks good. Feel free to merge it against master branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add ID for each T0 deployment.
The ID is the time and date of the deployment wiht the following format: ''%y%m%d%H%M%S"
The ID is stored in a new table in the T0AST database. The table preventscratend multiple IDs unless the DB is wiped out.
The deployment ID is also added to the Unique workflow name in replays