ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update page description metadata

This commit is contained in:
Laura Pacilio 2021-06-28 17:10:11 -04:00
parent 908ceec8c1
commit 5e89ac590e
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/intro/vs/boto.html.markdown
View File

@ -3,7 +3,7 @@ layout: "intro"
page_title: "Terraform vs. Boto, Fog, etc." page_title: "Terraform vs. Boto, Fog, etc."
sidebar_current: "vs-other-boto" sidebar_current: "vs-other-boto"
description: |- description: |-
Libraries like Boto, Fog, etc. are used to provide native access to cloud providers and services by using their APIs. Some libraries are focused on specific clouds, while others attempt to bridge them all and mask the semantic differences. Using a client library only provides low-level access to APIs, requiring application developers to create their own tooling to build and manage their infrastructure. How Terraform compares to cloud provider client libraries.
--- ---
# Terraform vs. Boto, Fog, etc. # Terraform vs. Boto, Fog, etc.
@ -21,4 +21,3 @@ how cloud resources and services should be created, provisioned, and
combined. Terraform is very flexible, using a plugin-based model to combined. Terraform is very flexible, using a plugin-based model to
support providers and provisioners, giving it the ability to support support providers and provisioners, giving it the ability to support
almost any service that exposes APIs. almost any service that exposes APIs.