aws-cli VS cookiecutter

The AWS CLI is a must-have tool if your team relies on Amazon Web Services. It lets you effortlessly interact with AWS services, orchestrate resource management, and automate tasks from the comfort of your terminal. Once you get used to the tool, you'll notice how convenient and quick it is to fit into your processes – especially compared to going through AWS's web-based user interface.

Just for your consideration, the network effect is very real with package managers, too:

https://search.nixos.org/packages?channel=23.05&show=awscli2 is 2.11.27 (even on the "unstable" channel), versus https://formulae.brew.sh/formula/awscli#default that is 2.12.1, which correctly is the most current (https://github.com/aws/aws-cli/tags)

s3fs allows Linux, macOS, and FreeBSD to mount an S3 bucket via FUSE(Filesystem in Userspace). s3fs makes you operate files and directories in S3 bucket like a local file system. s3fs preserves the native object format for files, allowing use of other tools like AWS CLI.

AFAIK it's still a Python package: https://github.com/aws/aws-cli/tree/2.11.6

Check CLI version, it looks like the earliest version that had DEEP_ARCHIVE support was 1.16.133 (https://github.com/aws/aws-cli/commit/55efab102f774ef17bf51ad32e939e4e03a5ff8a)

And this is the init_localstack.sh file content, a unique thing about localstack its that you can move all strings like an aws-cli tool, also the container deletes all the content and config once the container stops, so the script file must create all the resources that you need from Localstack

It can? I created a pull request for this that hasn't been merged yet: https://github.com/aws/aws-cli/pull/6365

Sometimes I use this to abstract boilerplate https://github.com/cookiecutter/cookiecutter

It can use a repo as a template.

It supports some interactive questions to choose options but mostly it is jinja templates.

Having libraries would be another option.

Install the cookiecutter package using the following command:

Consider taking a look at cookiecutter to generate projects from templates. There is also cookiecutter-django. As for your environment variables you should have an example .env file containing all the environment variables required by your project (without setting them) that can be safely pushed into your repository for you and other developers to copy into the actual .env file that'll be used by your project (add this file to .gitignore)

The Python Cookiecutter library revolutionizes project development by offering streamlined approach to creating template projects and improving developer experience.

We use cookie cutter templates (the Python project, https://github.com/cookiecutter/cookiecutter ), we prompt for the module & version etc

Why not use cookiecutter or a similar tool designed for making these sorts of project templates?

Is it common? I don't know. Is it useful? Absolutely. There is a tool called cookiecutter that allows you to define your own setup. For example, my cookiecutter setup for a python library is here. You can see what it's like by first installing the cookiecutter cli and then running

Also cookiecutter.

Visual Cookiecutter enhances the functionality of cookiecutter by offering unique features such as required fields, conditional input parameters, optional descriptions, and the ability to fix mistakes easily. This package seamlessly integrates with cookiecutter so that all existing templates work out-of-the-box.