profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/vaficionado/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Jon Schulman vaficionado @hashicorp Vacaville, CA Product Manager, Terraform Cloud

vmware/terraform-provider-vra7 38

Terraform VMware vRealize Automation 7 provider

vaficionado/cas-apis 8

VMware Cloud Assembly API Packages

vaficionado/terraform-kubernetes 6

Deploy a GKE K8s cluster with an optional flag to enable Consul and Vault via Helm charts

vaficionado/aws-demo-app 3

Demo AWS App

vaficionado/terraform-aws-notify-slack 1

Terraform module which creates SNS topic and Lambda function which sends notifications to Slack

vaficionado/aws-clarity-ghapp 0

Clarity-based Demo App on AWS

vaficionado/cas-blueprints 0

CAS Blueprints

vaficionado/github-actions 0

Test repo for Actions

vaficionado/jenkins-x 0

JenkinsX TF testing

push eventhashicorp/terraform-website

Chris Griggs

commit sha 58aa8dbed9cdda339e2502b27b1568f190211cd3

Update partner formatting (#1857) Updating to have partners listed in alphabetical order.

view details

push time in 3 days

delete branch hashicorp/terraform-website

delete branch : cgriggs01-update-docs

delete time in 3 days

PR merged hashicorp/terraform-website

Reviewers
Update partner formatting

Updating to have partners listed in alphabetical order.

+9 -9

1 comment

1 changed file

cgriggs01

pr closed time in 3 days

pull request commenthashicorp/terraform-website

Update partner formatting

Yeah, this is a simple reordering of content, I'm cool with this too. Merging

cgriggs01

comment created time in 3 days

issue commenthashicorp/terraform-provider-tfe

Why "tag_names", not "tags"?

Hi there @robinbowes and thanks for the note! I'm the product manager for the workspace tagging project we recently shipped, and I wanted to pop in and give you some context on why we made the decision we did here.

We on the project team spent weeks researching this exact question; whether "tags" should be key:value pairs or singletons, what the accepted industry definition of a "tag" vs a "label" was, and what kind of mental model our users wanted to apply to managing Terraform workspaces. One of the two things we learned for certain were that there's no consistent use of "tags" vs "labels" as a concept in the industry. And the second is that no matter which way we went - there would be some folks who definitely wanted the other!

That being said, a pattern started to emerge that the majority the users we spoke with see the Terraform platform as more similar to other information management tools than to the hyperscaler clouds themselves. These tools are more like (for example) Jira, Confluence, Gmail, Asana, etc. These tools implement singleton tags/labels that are more about grouping and managing metadata, and the pattern applied more cleanly to the Terraform Cloud workflows we wanted to enable.

However, you hit our conceptual workaround exactly - both the UI and API are built to allow you to use a separator character in your tag, so you can enter tags as key:value and parse them via the API or an external tool with minimal effort.

The whole team and I definitely appreciate and welcome your feedback on this 😄 However, in this case, since the tfe provider is just implementing what the platform exposes, I'd ask that you log this request through the Terraform Cloud support process so we can properly track it there. Feel free to reference this issue/comment/etc when you do so.

Thanks so much for using Terraform!

robinbowes

comment created time in 8 days

pull request commenthashicorp/terraform-website

Run checks

LGTM, thanks for the additional comments all

beekus

comment created time in 9 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha f825efce094e2b4f96f3e048b87653f31666c3fd

Update content/source/docs/cloud/workspaces/run-tasks.html.md Co-authored-by: Cameron Stitt <cstitt@hashicorp.com>

view details

push time in 9 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha 2ab2fd9221cf88679af8d7218e6c345561fe85a4

Update content/source/docs/cloud/users-teams-organizations/organizations.html.md Co-authored-by: Cameron Stitt <cstitt@hashicorp.com>

view details

push time in 9 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha cb0c990736bcc475deef4b1f9558106445fc1082

Update content/source/docs/cloud/run/states.html.md Co-authored-by: Cameron Stitt <cstitt@hashicorp.com>

view details

push time in 9 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha 80c41a4ba49055395fac7be6064dfd44de83607b

Update content/source/docs/cloud/overview.html.md Co-authored-by: Cameron Stitt <cstitt@hashicorp.com>

view details

push time in 9 days

Pull request review commenthashicorp/terraform-website

Run checks

+---+layout: "cloud"+page_title: "Terraform Cloud Run Tasks Integrations Setup"+description: |-+  Run tasks allow Terraform Cloud to execute tasks in external systems at specific points in the Terraform Cloud run lifecycle. ++---++# Run Tasks Integration

ok, done!

beekus

comment created time in 9 days

PullRequestReviewEvent

push eventhashicorp/terraform-website

Jon Schulman

commit sha 88a425dd351eb6d2ce4f1735c2d8a8a64e07826f

adding a beta note to this page as well

view details

push time in 9 days

Pull request review commenthashicorp/terraform-website

Run checks

+---+layout: "cloud"+page_title: "Terraform Cloud Run Tasks Integrations Setup"+description: |-+  Run tasks allow Terraform Cloud to execute tasks in external systems at specific points in the Terraform Cloud run lifecycle. ++---++# Run Tasks Integration

good point, i'll do that

beekus

comment created time in 9 days

PullRequestReviewEvent

push eventhashicorp/terraform-website

Jon Schulman

commit sha 2dfbb617bb778893f69e9d43c219046b2a4edd40

Update content/source/docs/cloud/api/run-tasks.html.md Co-authored-by: Cameron Stitt <cstitt@hashicorp.com>

view details

push time in 9 days

Pull request review commenthashicorp/terraform-website

Run checks

+---+layout: "cloud"+page_title: "Run Tasks - API Docs - Terraform Cloud and Terraform Enterprise"+---++[200]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/200+[201]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/201+[202]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202+[204]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204+[400]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400+[401]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401+[403]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403+[404]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404+[409]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/409+[412]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/412+[422]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/422+[429]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429+[500]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/500+[504]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/504+[JSON API document]: /docs/cloud/api/index.html#json-api-documents+[JSON API error object]: https://jsonapi.org/format/#error-objects++# Run Tasks API++-> Note: As of September 2021, Run Tasks are available only as a beta feature, and not all customers will see this functionality in their Terraform Cloud organization.

fair callout, i'll take this!

beekus

comment created time in 9 days

PullRequestReviewEvent

pull request commenthashicorp/terraform-website

Adding Structured Run Output docs

Thanks! @im2nguyen if you're pleased as well would you merge? appreciate it :)

vaficionado

comment created time in 21 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha 185f452f237548722ed1de774848cfe1315d67a1

update to flow for UI options

view details

push time in 21 days

Pull request review commenthashicorp/terraform-website

Adding Structured Run Output docs

 By default, new workspaces in Terraform Cloud do not allow other workspaces to a  -> **Note:** The default access permissions for new workspaces in Terraform Cloud changed in April 2021. Workspaces created before this change defaulted to allowing global access within their organization. These workspaces can be changed to more restrictive access at any time. Terraform Enterprise administrators can choose whether new workspaces on their instances default to global access or selective access. +### User Interface++Select the user experience for displaying plan and apply details. ++The default experience is *Structured Run Output*, which displays your plan and applies in a friendly, human-readable format. Each individually expandable node represents a resource, with the relevant details contained within. There are also expandable sections displaying any configured outputs.++~> **Note:** Your workspace must be configured to use a Terraform version of 1.0.5 or higher for the Structured Run Output experience to be fully supported. Workspaces running versions from 0.15.2 may see partial functionality. Workspaces running versions below 0.15.2 will default to the "Console UI" experience regardless of the User Interface setting.  ++The Console UI experience is the traditional Terraform experience, where live text logging is streamed in real time to the UI.

I'm cool with moving it up but I don't personally love the "alternatively..." phrasing since we're just enumerating the two available options and what they mean, and i think what I have here is more in line with other similar sections? If that's not true feel free to just change it from what I'm updating to now though!

vaficionado

comment created time in 21 days

PullRequestReviewEvent

push eventhashicorp/terraform-website

Jon Schulman

commit sha 65b2d34021c0491906513f7351fa7c70f970c9f6

Update content/source/docs/cloud/workspaces/settings.html.md thanks! i made one small change but this is cool by me Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>

view details

push time in 21 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha 65cd5e1bb0d33d497b5245c962a0b24881b961ff

Update content/source/docs/cloud/workspaces/settings.html.md

view details

push time in 21 days

Pull request review commenthashicorp/terraform-website

Adding Structured Run Output docs

 By default, new workspaces in Terraform Cloud do not allow other workspaces to a  -> **Note:** The default access permissions for new workspaces in Terraform Cloud changed in April 2021. Workspaces created before this change defaulted to allowing global access within their organization. These workspaces can be changed to more restrictive access at any time. Terraform Enterprise administrators can choose whether new workspaces on their instances default to global access or selective access. +### User Interface++Select the user experience for displaying plan and apply details. ++The default experience is *Structured Run Output*, which displays your plan and applies in a friendly, human-readable format. Each individually expandable node represents a resource, with the relevant details contained within. There are also expandable sections displaying any configured outputs.++~> **Note:** Your workspace must be configured to use a Terraform version of 1.0.5 or higher for the Structured Run Output experience to be fully supported. Workspaecs running versions from 0.15.2 may see partial functionality. Workspaces running versions below 0.15.2 will default to the "Console UI" experience regardless of the User Interface setting.  
~> **Note:** Your workspace must be configured to use a Terraform version of 1.0.5 or higher for the Structured Run Output experience to be fully supported. Workspaces running versions from 0.15.2 may see partial functionality. Workspaces running versions below 0.15.2 will default to the "Console UI" experience regardless of the User Interface setting.  
vaficionado

comment created time in 21 days

PullRequestReviewEvent

push eventhashicorp/terraform-website

Jon Schulman

commit sha c32b02a5df9bec30d7774bf127d34ad44d3bc1ef

Update content/source/docs/cloud/run/cli.html.md Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

view details

push time in 21 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha 794cf7bf6b4ab2cefb7e338559a13f14c3203eb4

Update content/source/docs/cloud/run/cli.html.md Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

view details

push time in 21 days

push eventhashicorp/terraform-website

Jon Schulman

commit sha f06ae27542ad5bd3788df4ae5473465892cec367

Update content/source/docs/cloud/workspaces/settings.html.md Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

view details

push time in 21 days

Pull request review commenthashicorp/terraform-website

Adding Structured Run Output docs

 By default, new workspaces in Terraform Cloud do not allow other workspaces to a  -> **Note:** The default access permissions for new workspaces in Terraform Cloud changed in April 2021. Workspaces created before this change defaulted to allowing global access within their organization. These workspaces can be changed to more restrictive access at any time. Terraform Enterprise administrators can choose whether new workspaces on their instances default to global access or selective access. +### User Interface++Select the user experience for displaying plan and apply details. ++The default experience is *Structured Run Output*, which displays your plans and applies in a friendly, human-readable format. Each resource will be respresented by an individually expandable node, with the relevant details contained within. Any configured outputs will also be displayed in their own expandable section.++-> **Note:** Your workspace must be configured to use a Terraform version of 1.0.5 or higher for the Structured Run Output experience to be fully supported. Workspaecs running versions from 0.15.2 may see partial functionality. Workspaces running versions below 0.15.2 will default to the "Console UI" experience regardless of the User Interface setting.  

Oh, that's weird. I literally copied this note syntax from one further up on the same page. You're the boss! However I also want to fix a typo I just noticed here (misspelling of "workspaces" in one instance)

vaficionado

comment created time in 21 days