Add tunneling options to slack-app-setup and enhance service mode configuration #1772
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 tunneling options to slack-app-setup and enhance service mode configuration
Enhancements
Advanced security configuration for streamlined service creation: Added CLI arguments for rate limiting (
-rl), encryption (-ek), and token expiration (-te) toservice-createcommand.Advanced security prompts in service-docker-setup: Added interactive prompts for advanced security options including IP filtering (allowed/denied lists), rate limiting, response encryption, and token expiration
Tunneling options for slack-app-setup: Added ngrok and Cloudflare configuration prompts to
slack-app-setupcommand. Public URLs are automatically constructed and stored in vault record for slack-app tunnelling reference.Updated default resource names: Changed all default names from "CSMD" prefix to "Commander Service Mode" for better clarity:
Bug Fixes
Fixed ngrok/cloudflare URLs left empty in service config.json and vault records: Previously,
ngrok_public_urlandcloudflare_public_urlwere not being constructed from custom domains. Now correctly builds URLs (e.g.,https://<custom-domain>.ngrok.ioorhttps://<subdomain>.<domain>.com) in both interactive and streamlined modes, and saves them to bothservice_config.jsonand the vault record's custom fields.Fixed rate limiting not working correctly for v2 API: Each API endpoint now has independent rate limit counters, and removed incorrect multiplier logic that was causing premature blocking
Fixed bypass master password message printed during service mode startup: Removed unnecessary debug/info message that was displayed every time service mode started