6 Commits (fbb0c88c218ea65cff8ea7028eaecbedfc1b5f4f)

Author	SHA1	Message	Date
Martin Atkins	0a5059df15	website: Stronger statements on when to use named workspaces ... In an earlier commit we added the "Best Practices" situation to try to clarify the intended uses of named workspaces and to warn against using them as an alternative to system decomposition. However, the prior statement was cautious in its recommendations in the interests of being pragmatic, and as a result we've seen that users have in some cases misunderstood or disregarded these recommendations. The new "When to use Multiple Workspaces" section aims to be more explicit that having multiple separate Terraform configurations is the preferred solution for many use-cases, and that workspaces are intended for a more limited set of use-cases around convenient development and testing. It also emphasizes the analogy to version control branches that was just a footnote in the prior text, to help the reader become familiar with the concept by relating it to a concept and workflow they are hopefully already familiar with. This new section also attempts to provide a more elaborate description of the proposed alternative when the goal is system decomposition. In the long run some of this content would probably be better placed elsewhere since it is useful advice even for users who never discover named workspaces, but it can live here for the time being to limit the scope of this change until we are ready to make more comprehensive revisions to the docs in this area. Finally, the introductory documentation here is adjusted slightly in preparation for the intended future expansion of workspaces to include stored variable values and, for more tailored backends like Terraform Enterprise, a full log of prior operations. More revisions will be required to cover the specifics of this later, but this new framing will hopefully help users form a mental model of named workspaces that has room for these future enhancements and the corresponding concept in Terraform Enterprise, rather than our previous framing that workspaces are fundamentally just named states.	8 years ago
Cameron Childress	5ebb9d818d	Workspaces are supported locally.	8 years ago
James Bardin	ccb90d5b6b	add gcs to the backends that support workspaces ... Also add the term "workspaces" to the `prefix` documentation.	8 years ago
Paul Stack	002200b8f1	websites/workspaces: Add Manta to the list of workspace backends (#16545) ... As Manta backend has now been merged, this should have been done in the same PR - apologises for that	9 years ago
Tom Harvey	25c3a879db	Adding `azurerm` to the list of supported backends (#16531) ... Fixes #16530	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split ... This repo now contains only the core docs, with other content moving elsewhere.	9 years ago