sec : key generation

[Jacob-Polane]

Issue: #4250

Implement dynamic SecurityKey generation in the starter-template-publisher.yml pipeline:

Replace static key with #{securityKey}# placeholder in config files
Generate unique 86-character alphanumeric key during pipeline run
Replace placeholder before archiving template
Each published template gets a unique SecurityKey

Benefits
✅ Each template build gets a unique JWT signing key
✅ Improved security for distributed templates
✅ No manual key generation required
✅ Source control maintains clean placeholder
✅ Automated and repeatable process

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (3)

• shesha-starter/backend/src/ShaCompanyName.ShaProjectName.Web.Host/app.config.json.pipeline is excluded by none and included by none
• shesha-starter/backend/src/ShaCompanyName.ShaProjectName.Web.Host/appsettings.json is excluded by none and included by none
• starter-template-publisher.yml is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}