Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
6 tasks
myii opened this issue Jun 12, 2019 · 1 comment
Open
6 tasks

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

myii opened this issue Jun 12, 2019 · 1 comment

Comments

@myii
Copy link
Member

myii commented Jun 12, 2019

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).

@windowsrefund
Copy link

After @myii helped me to get TOFS working, I plan on using my new understanding of this approach to update the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants