Skip to content

Work through remaining steps of TOFS implementation after PR #398 #417

@myii

Description

@myii

Transferring from #398 (comment):

  • README: Update to explain how TOFS can be used instead of pillar for master/minion configuration.
  • salt.cloud: (After due consideration) Use the same method to allow TOFS to be used for these configurations: cloud.maps.d, cloud.profiles.d & cloud.providers.d.
  • Deprecation step 1: Display deprecation warning when configuration is being done by pillar.
  • Deprecation step 2: Make TOFS the default, making pillar-based opt-in.
  • Deprecation step 3: Remove pillar-based method, with breaking change commit.
  • Alongside deprecation (at some point): Remove code to clean up old _defaults.conf file if they have it around -- all .conf files must be permitted, should a user choose to use that filename.

This comment is useful for explaining how TOFS can be used instead of pillar: #398 (comment).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions