5 Commits (3e3d8f6764dcfac8f3bb68bd4e1820cf98bb7bb6)

Author	SHA1	Message	Date
andrewjkeith	6cb9aaacfe	website: Fix extension_requests argument name for Puppet provisioner	7 years ago
Martin Atkins	e0d72930fa	website: Warn against using provisioners ... For a long time now we've been advising against the use of provisioners, but our documentation for them is pretty prominent on the website in comparision to the better alternatives, and so it's little surprise that many users end up making significant use of them. Although in the longer term a change to our information architecture would probably address this even better, this is an attempt to be explicit about the downsides of using provisioners and to prominently describe the alternatives that are available for common use-cases, along with some reasons why we consider them to be better. I took the unusual step here of directly linking to specific provider documentation pages about the alternatives, even though we normally try to keep the core documentation provider-agnostic, because otherwise that information tends to be rather buried in the provider documentation and thus the reader would be reasonable to use provisioners just because we're not giving specific enough alternative recommendations.	7 years ago
Lindsey Smith	a0f06826ab	website: Puppet provisioner docs links fixed (#21843)	7 years ago
Lindsey Smith	dcbdd70385	website: Clarifications to Puppet provisioner docs (#21810)	7 years ago
Tim Sharpe	2ab2796c93	website: Docs for the Puppet provisioner (#21792)	7 years ago