fix: create object encrypted file for versions #800
Merged
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.
🔧 Problem
We have an error in production when logged-in and going from old version back to the
2.4.0
in the selector.🍰 Solution
Add the encrypted file for objects when creating the version.
🚨 Points to watch/comments
I’ve modified the already published version by adding the encrypted
processes_impacts_object.json.enc
manually and redeployed the production, so it should be working now. We don't need to land this patch ASAP, it can wait for the next release.🏝️ How to test
We will only be able to test it in the next release.