Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TFE Output Logging #22441

Closed
milesmatthias opened this issue Aug 12, 2019 · 3 comments
Closed

TFE Output Logging #22441

milesmatthias opened this issue Aug 12, 2019 · 3 comments

Comments

@milesmatthias
Copy link

Would love to see any output resources logged in the terraform plan output on TFE. This would help with these common scenarios:

  1. developers to not be familiar with the CLI utilities when using TFE, because they push a new branch to a repo, TFE picks it up and plans / applies it.
  2. a workspace to use modules where you're trying to see values within a module and pushing a new branch of the workspace to see its TFE plan output

(to be clear, TFE being Terraform Enterprise)

@hashibot
Copy link
Contributor

Hello! 👋

This issue doesn't seem to be following one of the standard issue templates available from the "New Issue" page. The information requested in those templates is important for my human friends to fully understand what's going on.

Please feel free to open a new issue using either the Bug Report or Feature Request template, as appropriate, and then the Terraform maintainers will review it. Thanks!

Please note that we use GitHub issues for tracking bugs and enhancements rather than for questions. While we may be able to help with certain simple problems here it's better to use the community forum, where there are more people ready to help. The GitHub issues here are generally monitored only by our few core maintainers.

@teamterraform
Copy link
Contributor

It looks like this is covering similar use-cases as #15419, so let's use that existing issue to consolidate discussion about this general idea of including output values more explicitly in the plan phase.

@ghost
Copy link

ghost commented Sep 13, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants