install: handle failed module-map / resource catalog regeneration after a successful install #17
Labels
No labels
coordination/cross-repo
coordination/needed
effort
large
effort
medium
effort
small
meta/duplicate
meta/planning
meta/wontfix
priority
high
priority
low
priority
medium
session
blocker
session
handover
session
next
status
blocked
status
done
status
in-progress
status
review
status
to-go
type
admin
type
bug
type
config
type
deployment
type
docs
type
enhancement
type
feature
type
handover
type
infrastructure
type
installation
type
maintenance
type
migration
type
research
type
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DAW/daw-module-manager#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Revisit warnings and errors in the install flow once berhtjan-cli is
migrated: a failed follow-up step after a successful install must not
only be a warning.
Background
install() and install_local() call regen_module_map() after the package
is verified. If gen-module-map.sh fails, that is only a [WARN] and the
install is reported as successful. The resource catalogs
(DAW/daw-modul-berhtjan-core#13) will be regenerated at the same point;
a conflict introduced by a new module (resource_conflict) or an
incomplete default language would then also end up as a warning while
the old catalogs stay active and the new module's texts are missing.
Scope
resource catalogs), and what the user is told about the state
(module installed, catalogs/map not updated)
error/i18n migration of this repo
module-map and catalogs need regenerating after a manual removal
Notes
Waits for the berhtjan-cli migration; adjust together.
Related
DAW/daw-modul-berhtjan-core#13