Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
N
Nabu
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tomotools
  • Nabu
  • Issues
  • #85

Closed
Open
Opened Feb 20, 2020 by Pierre Paleo@paleo
  • Report abuse
  • New issue
Report abuse New issue

Config file: mechanism for keys names changing

In the nabu config file, some keys are likely to change (or be added/removed) in the future.

There is already a nabu_config_version in the [about] section.
Now we need a mechanism to access one given key with a future-proof way.

For example, if paganin_delta_beta is changed to delta_beta:

get_property(phase.DELTA_BETA) --> DELTA_BETA: {"2020.1": "paganin_delta_beta", "2020.2": "delta_beta"}

Edited Feb 20, 2020 by Pierre Paleo
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: tomotools/nabu#85