Configure secret-token key in service.conf

Bug #1418020 reported by Free Ekanayaka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Charm
Fix Released
Medium
Данило Шеган

Bug Description

The landscape section in service.conf should have an entry like:

[landscape]
secret-token = 2d3dbbcb171b6c3e5446922f4ef85f5d080ff5429addb0803

(code to generate it can be copied from c.l.scripts.standalone.plugins.upgrades.generate_secret_token)

this should be common across all units, so it should go into hooks.lib.relations.landscape.LandscapeLeaderContext.

NOTE: it seems at the moment this bit is not handled in the stable charm (perhaps and oversight).

Related branches

Changed in landscape-charm:
importance: Undecided → Medium
tags: added: upgradable-charm
Changed in landscape-charm:
assignee: nobody → Данило Шеган (danilo)
status: New → In Progress
tags: added: kanban
tags: removed: kanban
Changed in landscape-charm:
status: In Progress → Fix Committed
Changed in landscape-charm:
milestone: none → 1.0
Changed in landscape-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.