zeal VS terraform-provider-aws

There's also Zeal (https://zealdocs.org/) which is basically the same as Dash but open source and runs on non-Mac devices.

For offline tech documentation you can use Zeal. Must have tool for poor internet connection places. Present in ubuntu repos. https://zealdocs.org/

ads don't have to proprietary

here's one example of ads in FOSS https://github.com/zealdocs/zeal/issues/779

There’s stuff like https://zealdocs.org/ that allow you to take all relevant documentation with you so offline coding will work.

If you just want to be productive, you could also bring a lot of books or downloaded tutorials on a drive.

Btw, make sure your drive is encrypted and you think of a way to backup your data so you don’t lose the offline progress.

I’d suggest you look into Kiwix¹ and also Zeal².

1. https://www.kiwix.org/

2. https://zealdocs.org/

For offline documentation, I use Zeal (called Dash on macos) which looks/works almost identically to rubydoc.info but much faster since it's offline, has a standard interface for all installed language documentations, and only 1 global hotkey away while programming.

I highly recommend using local solutions to this local issue: Zeal[1] (aka Dash[2] on MacOS)

Load up the "docsets" of your languages (lightly edited HTML docs for indexing purposes) and use a global keyboard shortcut (F8 for me) to pull up Python/Postgres/Terraform docs, searching for the right function without internet query.

This isn't straight up applicable to all questions of course, but "How do I search regular expressions in Python again?" is now as easy as "re"

Note that the docsets can be converted from normal HTML ones via doc2dash[3], especially useful to load up custom docs like private providers.

[1]: https://zealdocs.org/

⚠ There is currently an issue where the additional_configuration block order causes differences when applying the Terraform configuration without making any changes.

For Terraform, instead, a new version of the AWS module supports a dedicated resource.

If we check the support for the Terraform AWS Provider here (state for the date of publishing this article), we will see that the service is not yet fully supported. Last week, after more than half a year, support for creating a policy store was added. Additionally, we have the configuration to add template policies. However, the identity source is in the form of a PR draft, and there is no PR yet for the ability to create policies.

https://github.com/hashicorp/terraform-provider-aws/issues/3...

The size is what you get when you add every single AWS Go client into one binary.

Each service client like 1-2MB. But when you have 200 services....

Issue with EC2 Instance Metadata running inside Container

Well, at least we now have a promising lead. Some diligent googling and browsing through Github issues in the AWS provider project yielded no directly related findings. However, I did come across a few recent bug reports about the recent change AWS made regarding the treatment of public buckets. And interestingly, they described precisely the behavior I was encountering.

Latest version of TF but seems to be same Issue as this which has already been submitted : https://github.com/hashicorp/terraform-provider-aws/issues/10611

Look at this; I think the provider is just screwed up: https://github.com/hashicorp/terraform-provider-aws/issues/28672