WEEKLY_UPDATES.md
Hey folks, the last week we've been impacted by several sicknesses and out of office colleagues. Nevertheless, we have made progress with several issues related to static evaluation. Specifically:
TOFU_ENABLE_STATIC_SENSITIVE=1 environment variable to enable the secure behavior.help wanted. These are issues open for a community member to contribute a PR and we'd love to review it.Well hello there! We have a week of housekeeping behind us, but also a few important changes:
ghcr.io/opentofu/opentofu will no longer be usable as a base image for custom container builds due to security reasons and will only be available as a CLI image. See the pull request for details.for_each, as well as -exclude.help wanted. These are issues open for a community member to contribute a PR and we'd love to review it.Hi there! It's been a busy month since the last "Weekly Update". Here are the latest updates:
for_each (this is part of the effort to extend the features related to the 1.8.0 early evaluation). We are working diligently to include these updates in the 1.9.0 release.-exclude flag RFC and almost done with implementing it for the upcoming release.help-wanted label, so keep an eye out for them! We opened a few in our registry-ui repository here.Here's what happened since the last update:
.tofu files with an override functionality, and enhancements to tofu test with provider mocking and resource overrides.for_each. Our goal is to include these updates in the 1.9.0 release.-exclude flag and started working on it. We aim to release it as part of the 1.9.0 release.help-wanted label, so keep an eye out for them!Hey folks, sorry for the sporadic updates, we'll try to make these more frequent. Here's what happened since the last update:
.tofu files with an override functionality. We are currently working towards a 1.8.0 release candidate.help-wanted issues on GitHub and Slack related to the registry UI.Hello! It's been a busy month since the last "Weekly Update" and there is a lot to cover!
tofu testvariables blocktofu {} block as alternative to terraform {} and change understanding of required_versionhelp-wanted label, so keep an eye out for them!Hello there! After the 1.7.1 release last week, the core team has been focusing on a few remaining issues for 1.7.2 and starting to look forward to 1.8!
help-wanted label, so keep an eye out for them!Hello there! Again after a break in updates, since most weeks we've had preview or stable releases, which summed up most of what happened.
We haven't slowed down, and managed to get the stable release out according to schedule, before the end of April! Since then, we've got a few bug reports and already released a follow-up 1.7.1 release. Now, we're primarily working towards the 1.8 release.
help-wanted label, so keep an eye out for them!Hey there! First, apologies for the lack of updates over the last two weeks, we've been a bit busy with the Cease and Desist Letter we got. That's fortunately all sorted now, and we're fully back to engineering work this week! All of this delayed 1.7 by around a week, but this delay also gave us some additional time to add cool unique features to provider-defined functions in OpenTofu!
Importantly, we're planning to get a 1.7.0-beta1 release out tomorrow!
Additionally, we'll have a livestream to showcase some cool stuff next week on Wednesday!
tofu test-related issues, though it might not make it's way into 1.7.Hello there! We've had a fairly quiet couple days after KubeCon last week, but still managed to make progress in some key areas!
Hey there! We released OpenTofu 1.7.0-alpha1 end of last week and most of the team spent the week at OpenTofu Day Europe and KubeCon. You can find the videos on YouTube. Attendance was high, 150+ people (more than available seats).
Here's what we worked on:
Hey there! The main goal this week is getting an alpha release of 1.7 out, and you can expect it by the end of the week. It will include state encryption and the new removed block as major features, so that you can take those features for a spin and give us feedback.
Additionally, next week is KubeCon, and as part of it, OpenTofu Day! If you're going to KubeCon, make sure to come and say hi!
tofu test-related improvements for provider blocks.Hello there! This week we got state encryption running on the main branch for the first time, and we are planning to release an alpha build next week with a passphrase key provider and possibly the AWS KMS integration.
Hello! Over the last week we've finished up a couple of features, and we're continuing to work our way towards 1.7.0.
We've also just released 1.6.2 with a fix for a bug in tofu test.
Additionally, if you're coming to KubeCon and will be there a day early, make sure to come to OpenTofu Day! It's happening on Tuesday, the 19th of March, as a KubeCon + CloudNativeCon Europe CNCF-hosted Co-located Event. You can find more details here.
good-first-issue and help-wanted labels to find issues we've deemed are the best to pick up for external contributors. They are generally picked up quickly, so there might not be any available when you look. Please take a look there periodically if you'd like to find an issue to contribute to.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey there! Last week was quiet due to most of the core team is off on winter holidays, but this week we're all back!
good-first-issue and help-wanted labels to find issues we've deemed are the best to pick up for external contributors. They are generally picked up quickly, so there might not be any available when you look. Please take a look there periodically if you'd like to find an issue to contribute to.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
The last two weeks we've been focusing on working towards the 1.7.0 release, and on going through our issue backlog.
This weekend some of us have been to FOSDEM and had a stand there - it was amazing to hear in person how many people have already migrated to OpenTofu! We've also distributed a lot of OpenTofu t-shirts and stickers!
Additionally, most of the core team is off on winter holidays this week, so it's fairly quiet.
good-first-issue and help-wanted labels to find issues we've deemed are the best to pick up for external contributors. They are generally picked up quickly, so there might not be any available when you look. Please take a look there periodically if you'd like to find an issue to contribute to.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
This week we've been focusing on work related to the 1.6.1 release, the 1.7.0 release, and on going through our issue backlog.
On an unrelated note, we'll have a stand at FOSDEM and will have OpenTofu t-shirts and stickers, so if you're there, come say hi!
tofu show command on a legacy state file.removed block,for_each in the import block.good-first-issue and help-wanted labels to find issues we've deemed are the best to pick up for external contributors. They are generally picked up quickly, so there might not be any available when you look. Please take a look there periodically if you'd like to find an issue to contribute to.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey there! Long time no see in these weekly updates! We've skipped them during the holidays and the release week, but now we'll be back to the regular cadence.
Much has happened over the last few weeks, with the biggest news being the OpenTofu Stable 1.6 Release last week!
Since the stable release, we've been working to get 1.6.1 and 1.7.0 into your hands. We've also seen immense community interest, with members of the community contributing great changes, and others integrating it into third party tooling. This is all amazing, and we really appreciate it!
good-first-issue and help-wanted labels to find issues we've deemed are the best to pick up for external contributors. They are generally picked up quickly, so there might not be any available when you look. Please take a look there periodically if you'd like to find an issue to contribute to.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey there!
This week's been mostly about delivering that last 1% of work before we can publish a release candidate. Other than that, we've also started planning work for past the stable release, so targeting the 1.7 release.
The steering committee has also gathered (you can find the details here) and planned the official date for the stable release to be the 10th of January.
opentofu, but ended up rolling that back, and (softly) deprecating the whole concept of namespace-less provider references altogether, due to the edge-cases involved.tofu init with your projects to double-check everything you use is available in the registry.good-to-pick-up, to find issues we've deemed are the best to pick up for external contributors.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey there, time for a weekly update!
There was no update last week, but the important bit was that we've released the first beta release!
Going into more details:
registry.opentofu.org. It's receiving meaningful usage and working very well.tofu init on your codebases, and make sure that all providers and modules you're using are available. We did our best to make it a drop-in replacement, but we might've missed a provider or two. We're constantly monitoring 404 responses on our side and will back-fill anything that's missing.tofu init with your projects to double-check everything you use is available in the registry.good-to-pick-up, to find issues we've deemed are the best to pick up for external contributors (there are none available at this moment).Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hello!
Another week another update! This week has been very steady. We've been moving forward with the stable registry, and there's been no surprises so far.
Additionally, a new engineer has joined the OpenTofu Core Team and will be 100% dedicated to OpenTofu development. Welcome, @janosdebugs!
good-to-pick-up, to find issues we've deemed are the best to pick up for external contributors (there are none available at this moment).Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey there!
This last week has seen work on multiple avenues. More concretely, we've been steadily working our way down the stable release milestone. With the current pace, we expect the stable release to be out between mid-December and mid-January, preceded by a release candidate and a beta release.
good-to-pick-up, that should help you find issues we've deemed are the best to pick up for external contributors. However, all such issues have promptly been picked up, so there aren't any available at this time.Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey!
Big week for OpenTofu! The technical steering committee met and chose a registry design. We'll now be writing more detailed designs and then proceed with implementing the registry.
Moreover, two engineers have joined the OpenTofu Core Team and will be 100% dedicated to OpenTofu development. Welcome, @kislerdm and @cam72cam!
Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey!
This week was still mostly spent on discussing and implementing proof of concepts for some stable registry designs, as well as work on the S3 backend.
Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey!
This week was again spent on discussing and PoC'in stable registry designs, as well as work on the S3 backend.
brew install opentofu to use it!Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hello there!
This past week was mostly spent on creating stable registry designs, which is a prerequisite to building a stable provider/module registry and releasing a stable version of OpenTofu.
Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey!
Last week we've released the first alpha release (and another one the next day). This has been a huge milestone for the OpenTofu community, and means that you can actually download OpenTofu and play with it. It also marks the beginning of the stable registry design discussions.
Just to give you some metrics about the release:
We'll also have our first office hours today! Make sure you don't miss that.
Please let us know if you have any feedback on what we could improve, either with these updates or more generally - this very document was a result of such feedback! We're available on Slack, via GitHub issues, or even in the pull request updating this file.
Hey!
Another week, another update! This last week has been all about the alpha release, which is planned to be released this week, ideally tomorrow (Tuesday).
x.y.z and vx.y.z are supported, while we only support one of them.Please let us know if you have any feedback on what we could improve, either with these updates or more generally! We're available on Slack, via GitHub issues, or even in the pull request creating this very file.
Hello!
We’ve received some feedback that it’s currently hard to track the status of OpenTofu and what is currently being worked on. We hear you, and we’ll do better. We’re slowly moving discussions from our internal slack to public GitHub issues, to make them more inclusive. In addition, we’ll now be publishing an update like this once a week to give you a breakdown of where we’re at, what we’re currently working on, how you can best help, and what’s up next.
Please let us know if you have any feedback on what we could improve, either with these updates or more generally! We're available on Slack, via GitHub issues, or even in the pull request creating this very file.