jaxxstorm

you appear to be describing a peer relay: https://tailscale.com/docs/features/peer-relay

Note: I'm a tailscale employee

We have webhooks already for nodes added, but you could also use https://github.com/jaxxstorm/sentinel

I lead the customer engineering org at Tailscale.

We think this is a great idea and we're discussing internally potentially adding that to the console.

In the meantime, if you'd like to get an assessment, please feel free to open a support ticket (https://tailscale.com/contact/support?type=other&subject=sec...) and we'll happily take a look

There’s a lot wrong here, but the fact the author is upset there’s no confirmation for an API call makes me question if they should have any credentials, never mind staging

I wrote a POC for using Tailscale serve and funnel similarly to ngrok here:

https://github.com/jaxxstorm/tgate

Author of the post here.

It's always been relatively shocking to me that this is still relevant 4 years after I wrote it. Helm is as Ubiquitous as ever, despite attempts to replace it with Jsonnet, Cue and programming languages.

I've personally moved on from Jsonnet and would recommend Pulumi to anyone experiencing this problem.

Every single person who has this "you don't need state" take on IaC seems to be missing one key point.

They haven't built it, because it's really really hard to do.

We are happy to help over slack.pulumi.com

Terraform was (and I assume currently, OpenTF) under an MPL license, which is not currently compatible with the approved licenses that the CNCF supports: https://github.com/cncf/foundation/blob/main/allowed-third-p...

For them to get accepted into the CNCF would require relicensing a large amount of MPL work. What's always been confusing to me about Hashicorp's change and any subsequent relicense of OpenTF is that I know for a fact not everyone who contributed code to Terraform signed the CLA and allowed permission to relicense.

I suspect if OpenTF tries to relicense to a more permissive license like Apache 2 (rather than less in the case of BSL) license we might see some fireworks.

thanks, I've been through and fixed some issues, but any others you find please let me know!

thanks for the feedback!

this is absolutely not the experience we have when customers migrate to Pulumi, and I spend all day helping users undergo that transition.

I'm a a Pulumi employee, if you'd like to chat about how we can help add support, email me lbriggs[at]pulumi.com

Well, Pulumi is declarative, so I don’t really understand where this is coming from

You would need to bridge the Terraform provider to a Pulumi provider first. If you've written a Terraform provider, bridging to a Pulumi provider should be straightforward.

If you need help with this, please reach out to me on the Pulumi community slack at https://slack.pulumi.com and happy to help

You build a multi language component: https://www.pulumi.com/blog/pulumiup-pulumi-packages-multi-l...

You can then publish a language SDK for your supported languages, so npm for node packages, pip for python.

The invoking peer needs to have the language they're using runtime locally

The python boilerplater is here: https://github.com/pulumi/pulumi-component-provider-py-boile...

Here's an example component built in Go: https://github.com/jaxxstorm/pulumi-productionapp

Then in examples you can see it being using: https://github.com/jaxxstorm/pulumi-productionapp/tree/main/...

Pulumi employee here!

Worth noting that while lots of insights are leveraging LLMs/AI, it's only one pillar of the launch today.

The cross cloud search and analytics are really valuable additions to the product. On day 1, being able to export all your resource definitions to BI intelligence tools and drill down into specific areas of interest is something that has traditionally been very difficult.

On a personal note, being able to simply search for "who spun up this EC2 instance" without traversing through cloudtrail is a godsend, too.

> Upgrades without restarting: Sozu is always-up, meaning it upgrades itself while still processing requests.

How?