Making unencrypted sap client credentials nullable #2236
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.
Description:
made unencrypted credentials nullable so after removing refs tests can run
this PR must only be merged when
1st Removing decrypted client secret in sap configuration from code #2228 (merged)
then
2nd Migration for removing decrypted client secret in sap configuration #2230 (merged)
then
3rd Added encrypted client secret in sap configuration #2231 (merged)
and then
4th Data migration for encrypted credentials column in sap configuration #2215 (merged)
gets deployed
JIRA:
https://2u-internal.atlassian.net/jira/software/c/projects/ENT/issues/ENT-8972