opentofu / setup-opentofu Goto Github PK

License: Mozilla Public License 2.0

Shell 0.66% JavaScript 99.34%

setup-opentofu's Introduction

OpenTofu

OpenTofu is an OSS tool for building, changing, and versioning infrastructure safely and efficiently. OpenTofu can manage existing and popular service providers as well as custom in-house solutions.

The key features of OpenTofu are:

Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
Execution Plans: OpenTofu has a "planning" step where it generates an execution plan. The execution plan shows what OpenTofu will do when you call apply. This lets you avoid any surprises when OpenTofu manipulates infrastructure.
Resource Graph: OpenTofu builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, OpenTofu builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what OpenTofu will change and in what order, avoiding many possible human errors.

Getting help and contributing

Have a question? Post it in GitHub Discussions or on the OpenTofu Slack!
Want to contribute? Please read the Contribution Guide.
Want to stay up to date? Read the weekly updates, TSC summary, or join the community meetings on Wednesdays at 14:30 CET / 8:30 AM Eastern / 5:30 AM Western / 19:00 India time on this link: https://meet.google.com/xfm-cgms-has (📅 calendar link)

Tip

For more OpenTofu events, subscribe to the OpenTofu Events Calendar!

Reporting security vulnerabilities

If you've found a vulnerability or a potential vulnerability in OpenTofu please follow Security Policy. We'll send a confirmation email to acknowledge your report, and we'll send an additional email when we've identified the issue positively or negatively.

Reporting possible copyright issues

If you believe you have found any possible copyright or intellectual property issues, please contact [email protected]. We'll send a confirmation email to acknowledge your report.

License

Mozilla Public License v2.0

setup-opentofu's People

Contributors

Stargazers

Watchers

Forkers

kislerdm imjasonh cfacorp nicolas-brousse kaiju liatrio

setup-opentofu's Issues

Expose the number of changes (import/create/update/delete) via the wrapper

The current wrapper today exposes some output information about the execution of the command.

It would be nice to add some additional output including the number of resources to be:

imported
created
modified
deleted

I for execute some conditions based on those numbers and today I'm getting them parsing the out. I think it would be nice to include them in the setOutput of the wrapper already.

Let me know what you think

[Enhancement] Add github API token to make api calls

Problem

Github API quota is exceeded during tests.

Proposed solution

Add the github installation access token as request header in the fetchReleases function.

[enhancement] Remove the debugging output emitted by default

Problem

The debugging logs will be emitted by default. For example:

Plan: 1 to add, 0 to change, 0 to destroy.
neon_project.this: Creating...
neon_project.this: Creation complete after 1s [id=blue-cloud-40428863]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
::debug::OpenTofu exited with code 0.

Proposed Solution

Make debugging logs optional. They could be activated following the github instructions.

Automate release process

Problem

The release artefacts were prepared manually in a local env, this is highly error prone.

Proposed Solution

Define a release github workflow. See the one hashicorp use as an example.

Followup on #2 (comment).

Enhance release.js tests to calling github API

Problem

The test release.js mocks HTTP calls to github API wrongly. It led to testing side effects and unnecessarily quota consumption, see example.

Proposed Solution

Fix the "unhappy path" tests relying on the mock function fetchReleases

As a nit, nock can be removed from dependencies because it's not used.

Fix the stdout content with active wrapper

As a user of the setup-opentofu action, I want to rely on it when using the wrapper for stdout processing.

Problem

The tofu stdout's content captured by the wrapper is prefixed with the command yielding it. Apparently, it's caused by the default behaviour of @actions/exec: see the condition.

Proposed solutions

Propagate stdout/err without relying on @action/exec. See new release of setup-terraform and the fix for context.

Verified creator flag in GitHub Marketplace

Hello guys.

Would it be possible to make opentofu/setup-opentofu marked as "Verified creator" in GitHub Marketplace please?

Example (https://github.com/marketplace/actions/renovate-bot-github-action):

Thank you...

Update GitHub Action Branding from Legacy Terraform Color Scheme

What and Why:

Change legacy GitHub Action branding to reflect OpenTofu color scheme:

Before:

branding:
  icon: 'terminal'
  color: 'purple'

After:

branding:
  icon: 'trending-up'
  color: 'yellow'

opentofu / setup-opentofu Goto Github PK

setup-opentofu's Introduction

OpenTofu

Getting help and contributing

Reporting security vulnerabilities

Reporting possible copyright issues

License

setup-opentofu's People

Contributors

Stargazers

Watchers

Forkers

setup-opentofu's Issues

Problem

Proposed solution

Problem

Proposed Solution

Problem

Proposed Solution

Problem

Proposed Solution

Problem

Proposed solutions

What and Why:

Recommend Projects

Recommend Topics

Recommend Org