jinjaform | Terraform wrapper with Jinja2 templates | Infrastructure Automation library

by claranet Python Version: 0.5.4 License: MIT

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

kandi X-RAY | jinjaform Summary

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

Jinjaform is a transparent Terraform wrapper written in Python that adds Jinja2 template rendering and other features aimed at making Terraform projects easier to use.

Support

Quality

Security

License

Reuse

Support

jinjaform has a low active ecosystem.

It has 28 star(s) with 5 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 17 have been closed. On average issues are closed in 73 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jinjaform is 0.5.4

Quality

jinjaform has 0 bugs and 0 code smells.

Security

jinjaform has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jinjaform code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jinjaform is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jinjaform releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

jinjaform saves you 323 person hours of effort in developing the same functionality from scratch.

It has 776 lines of code, 44 functions and 10 files.

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

Top functions reviewed by kandi - BETA

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

Render the template
Generator that yields all the commands in a Jinjaformrc file
Defines a variable
Remove current thread
Create the terraform workspace
Start threads
Add a template
Populate the project
Setup s3 bucket
Return a boto3 session
Return default session
Check if the remote is changed
Abort the check
Setup AWS credentials
Find the terraform binary
Check if git is clean
Check if git is in the desired branch
Find the project root
Remove Terraform

Get all kandi verified functions for this library.

jinjaform Key Features

No Key Features are available at this moment for jinjaform.

jinjaform Examples and Code Snippets

No Code Snippets are available at this moment for jinjaform.

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 jinjaform

Install Jinjaform with Python pip, .e.g. pip install jinjaform. Jinjaform requires a .jinjaformrc file in the root directory of your Terraform project. When you run jinjaform it will look for this file in the current or parent directories. If .jinjaformrc is not found in the directory tree, it will suggest running jinjaform create to create one. This will create a file that will suit most projects. This file can be edited to suit your project and should be committed to version control.
The simplest way to set AWS credentials is like so:. Terraform does not ordinarily support profiles with MFA prompts, but Jinjaform does. It also uses boto-source-profile-mfa to cache and reuse MFA tokens.
Jinjaform finds the default AWS provider, uses the profile to get AWS credentials, and then exports them as environment variables.
Terraform ignores the profile argument when credentials are set with environment variables.

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: