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

Allow user to turn off variable substitution in Terraform files #5573

Closed
benPearce1 opened this issue May 17, 2019 · 2 comments

Comments

@benPearce1
Copy link

commented May 17, 2019

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.

Prerequisites

  • I have searched open and closed issues to make sure it isn't already requested
  • I have written a descriptive issue title
  • I have linked the original source of this feature request
  • I have tagged the issue appropriately (area/*, kind/enhancement)

The enhancement

When executing a Terraform step against a package, variables in package matching the following patterns will automatically have variable substitution run against them.

*.tf
*.tf.json
*.tfvars
*.tfvars.json

This enhancement adds the ability to turn this off and specify the files explicitly in the Target files field.

Mockup

image

@benPearce1 benPearce1 self-assigned this May 17, 2019
@benPearce1 benPearce1 added this to the 2019.5.4 milestone May 17, 2019
@benPearce1

This comment has been minimized.

Copy link
Author

commented May 17, 2019

Release note: Added ability to turn off variable substitution for Terraform default files in package

@benPearce1 benPearce1 closed this May 17, 2019
@octoreleasebot octoreleasebot removed this from the 2019.5.4 milestone May 17, 2019
@benPearce1 benPearce1 added this to the 2019.5.4 milestone May 17, 2019
@lock

This comment has been minimized.

Copy link

commented Aug 15, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.