Add a scoped newsletter API user for the scheduled campaign task
Token is generated once and kept in Secret listmonk-newsletter-api. Tested: create, test-send and schedule work; subscribers/settings 403. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -81,6 +81,16 @@ listmonk_api_role: Membership sync
|
||||
listmonk_api_lists:
|
||||
- eom.dev
|
||||
|
||||
# API user for the scheduled newsletter task: create, edit and schedule
|
||||
# campaigns to listmonk_newsletter_api_lists; no subscriber data or settings.
|
||||
# Its token is generated once and kept in Secret <name>-newsletter-api
|
||||
# (keys: url, username, token) for the task to read with kubectl.
|
||||
listmonk_newsletter_api_enabled: true
|
||||
listmonk_newsletter_api_user: newsletter
|
||||
listmonk_newsletter_api_role: Newsletter automation
|
||||
listmonk_newsletter_api_lists:
|
||||
- eom.dev
|
||||
|
||||
# Drop the sample lists, subscribers and campaign created by --install.
|
||||
listmonk_remove_sample_data: true
|
||||
|
||||
|
||||
Reference in New Issue
Block a user