Conversation
|
Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/lib-play/job/PR-644/1/scoverage-report/ |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughModified jwtSalt initialization in FlowActionInvokeBlockHelper to use an optional jwt.salt configuration parameter with a fallback to the required JWT_SALT environment variable, enabling configuration override while maintaining backward compatibility. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/lib-play/job/PR-644/2/scoverage-report/ |
When moving services away from environment provider to SSM, we use idiomatic names for typesafe config keys. JWT_SALT becomes jwt.salt in SSM, as JWT_SALT as a config key name is misleading as it indicates an environment setting. To make it work currently, services set
JWT_SALT = ${?JWT_SALT}.Summary by CodeRabbit