terraform-wrapper | Claranet France Terraform Wrapper | Infrastructure Automation library

by claranet Python Version: v12.2.0 License: MPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | terraform-wrapper Summary

terraform-wrapper is a Python library typically used in Devops, Infrastructure Automation, Terraform applications. terraform-wrapper has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has low support. However terraform-wrapper build file is not available. You can install using 'pip install terraform-wrapper' or download it from GitHub, PyPI.

tfwrapper is a python wrapper for Terraform which aims to simplify Terraform usage and enforce best practices.

Support

Quality

Security

License

Reuse

Support

terraform-wrapper has a low active ecosystem.

It has 109 star(s) with 15 fork(s). There are 15 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 9 have been closed. On average issues are closed in 79 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of terraform-wrapper is v12.2.0

Quality

terraform-wrapper has 0 bugs and 0 code smells.

Security

terraform-wrapper has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

terraform-wrapper code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

terraform-wrapper is licensed under the MPL-2.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

terraform-wrapper releases are available to install and integrate.

Deployable package is available in PyPI.

terraform-wrapper has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

terraform-wrapper saves you 606 person hours of effort in developing the same functionality from scratch.

It has 3118 lines of code, 168 functions and 21 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed terraform-wrapper and discovered the below as its top functions. This is intended to give you an instant insight into terraform-wrapper implemented functionality, and help decide if they suit your requirements.

Runs a command on each stack
Load stack configuration from file
Detects a configuration directory
Detect parent directories
Set the current session context
Perform a GET request
Returns the credentials for a given profile
Launch a CLI command
Get or create a session
Set the session context
Load wrapper configuration
Get a value from a dictionary
Select the terraform version
Return the last version of the terraform
Run Terraform
Run terraform
Download a Terraform provider
Search for GitHub releases on GitHub
Bootstrap the wrapper
Determine the root directory for a given stack
Run terraform command
Return the directory for the given stack
Return the path to the config file
Get the architecture
Parse command line arguments
Load the configuration from a yaml file
Detects the configuration directory at the specified location
Detect all parent directories in the wrapper config
Check for GKE credentials
Set terraform variables

Get all kandi verified functions for this library.

terraform-wrapper Key Features

No Key Features are available at this moment for terraform-wrapper.

terraform-wrapper Examples and Code Snippets

No Code Snippets are available at this moment for terraform-wrapper.

Community Discussions

Trending Discussions on Infrastructure Automation

Create CloudFormation Yaml from existing RDS DB instance (Aurora PostgreSQL)

Azure DevOps CI with Web Apps for Containers

QUESTION

Create CloudFormation Yaml from existing RDS DB instance (Aurora PostgreSQL)

Asked 2020-Jun-05 at 00:59

I have an RDS DB instance (Aurora PostgreSQL) setup in my AWS account. This was created manually using AWS Console. I now want to create CloudFormation template Yaml for that DB, which I can use to create the DB later if needed. That will also help me replicate the DB in another environment. I would also use that as part of my Infrastructure automation.

...

ANSWER

Answered 2020-Jun-05 at 00:59

Unfortunately, there is no such functionality provided by AWS.

However, you mean hear about two options that people could wrongfully recommend.

CloudFormer

CloudFormer is a template creation beta tool that creates an AWS CloudFormation template from existing AWS resources in your account. You select any supported AWS resources that are running in your account, and CloudFormer creates a template in an Amazon S3 bucket.

Although it sounds good, the tool is no longer maintained and its not reliable (for years in beta).

Importing Existing Resources Into a Stack

Often people mistakenly think that this "generates yaml" for you from existing resources. The truth is that it does not generate template files for you. You have to write your own template which matches your resource exactly, before you can import any resource under control to CloudFormation stack.

Your only options is to manually write the template for the RDS and import it, or look for an external tools that could reverse-engineer yaml templates from existing resources.

Source https://stackoverflow.com/questions/62206364

QUESTION

Azure DevOps CI with Web Apps for Containers

Asked 2020-Mar-16 at 08:59

I'm struggling to set up a CI process for a web application in Azure. I'm used to deploying built code directly into Web Apps in Azure but decided to use docker this time.

In the build pipeline, I build the docker images and push them to an Azure Container Registry, tagged with the latest build number. In the release pipeline (which has DEV, TEST and PROD), I need to deploy those images to the Web Apps of each environment. There are 2 relevant tasks available in Azure releases: "Azure App Service deploy" and "Azure Web App for Containers". Neither of these allow the image source for the Web App to be set to Azure Conntainer Registry. Instead they take custom registry/repository names and set the image source in the Web App to Private Registry, which then requires login and password. I'm also deploying all Azure resources using ARM templates so I don't like the idea of configuring credentials when the 2 resources (the Registry and the Web App) are integrated already. Ideally, I would be able to set the Web App to use the repository and tag in Azure Container Registry that I specify in the release. I even tried to manually configure the Web Apps first with specific repositories and tags, and then tried to change the tags used by the Web Apps with the release (with the tasks I mentioned) but it didn't work. The tags stay the same.

Another option I considered was to configure all Web Apps to specific and permanent repositories and tags (e.g. "dev-latest") from the start (which doesn't fit well with ARM deployments since the containers need to exist in the Registry before the Web Apps can be configured so my infrastructure automation is incomplete), enable "Continuous Deployment" in the Web Apps and then tag the latest pushed repositories accordingly in the release so they would be picked up by Web Apps. I could not find a reasoble way to add tags to existing repositories in the Registry.

What is Azure best practice for CI with containerised web apps? How do people actually build their containers and then deploy them to each environment?

...

ANSWER

Answered 2020-Mar-16 at 08:59

Just set up a CI pipeline for building an image and pushing it to a container registry.

You could then use both Azure App Service deploy and Azure Web App for Containers task to handle the deploy.

The Azure WebApp Container task similar to other built-in Azure tasks, requires an Azure service connection as an input. The Azure service connection stores the credentials to connect from Azure Pipelines or Azure DevOps Server to Azure.

I'm also deploying all Azure resources using ARM templates so I don't like the idea of configuring credentials when the 2 resources (the Registry and the Web App)

You could also be able to Deploy Azure Web App for Containers with ARM and Azure DevOps.

How do people actually build their containers and then deploy them to each environment?

Kindly take a look at below blogs and official doc which may be helpful:

Source https://stackoverflow.com/questions/60693622

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install terraform-wrapper

build-essential (provides C/C++ compilers)
libffi-dev
libssl-dev
python3 >= 3.6.2 <4.0 (3.8+ recommended)
python3-dev
python3-venv
Terraform 1.0+
An AWS S3 bucket and DynamoDB table for state centralization in AWS.
An Azure Blob Storage container for state centralization in Azure.
tfwrapper should installed using pipx (recommended) or pip:.
Add the following to your shell's interactive configuration file, e.g. .bashrc for bash:. You can then press the completion key (usually Tab ↹) twice to get your partially typed tfwrapper commands completed. Note: the -e tfwrapper parameter adds an suffix to the defined _python_argcomplete function to avoid clashes with other packages (see https://github.com/kislyuk/argcomplete/issues/310#issuecomment-697168326 for context).
If you used versions of the wrapper older than v8, there is not much to do when upgrading to v8 except a little cleanup. Indeed, the wrapper is no longer installed as a git submodule of your project like it used to be instructed and there is no longer any Makefile to activate it.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: