Description
The documentation for Installing Salt for development feels like it's out of date https://docs.saltstack.com/en/latest/topics/development/hacking.html . One example is that it seems to indicate that Python2 should be used:
On Arch Linux, where Python 3 is the default installation of Python, use the virtualenv2 command instead of virtualenv.

Currently, facades implement good exception handling, but resource parsing does not. That means that for a given resource type, if parsing fails for any given resource, the fetch_all method fails and stops, hence not parsing any additional resources.

All resources should be reviewed and updated, to ensure they handle parsing errors.

e.g., for AWS IAM roles (https://github.com/nccgroup/Scou

Hi, I read example command here https://docs.microsoft.com/en-us/cli/azure/container?view=azure-cli-latest#examples

and I found wrong command on "Create a container in a container group that runs Windows, with 2 cores and 3.5Gb of memory." Section.

Here your command
az container create -g MyResourceGroup --name myapp --image myimage:latest --ip-address public --ports 8081 --protocol UDP

Describe the bug
We have many tests that run assertions at the callback of Flow outputs.

This is dangerous because it can easily lead to false positives!

We need to add in the conftest.py a fixture that guarantees that it can be used to automatically ensure it is called (and the rest of the asserts are run)

Look at this PR:

jina-ai/jina#1385

A gui for ssh-copy-id maybe?

and as the tittle says, support for ed25519 keys, maybe a dropdown menu that lets you choose the ehh... cipher is it? for generating a new one. Or at least the ability to connect using them.

This would be really useful for users who are getting the hang of this.

Filtering by command is great, but how about also filtering by currently active directory?
I've quickly hammered something into place that works using preexec...

# Added to end of  ~/.bashrc

__peri_filter_preexec() { if [[ "${PWD}" =~ .*Private.* ]] ; then __BH_SAVE_COMMAND=''; fi }
if [ -f ~/.bashhub/deps/bash-preexec.sh ]; then source  ~/.bashhub/deps/bash-preexec.sh ; preexec_f

Right now a lot of the logging from the tasks does not get propagated back to the user, so we should make sure that all of the tasks are adding logs and errors to the results so that at minimum the data gets put into the worker-log.txt. Ideally we would store this info in datastore so that the clients could query it later (this part is in #115).

#22 introduced a feature to guess actions that are similar to an existing policy. It currently doesn't support all actions.

Here's things I currently know are missing (comment if you find more):

• KMS: Encrypt, Decrypt, GenerateDataKey, ...
• ECR: BatchDeleteImage, BatchGetImage, ...
• *Deregister*
• *Modify*
• *Remove*
• API Gateway: (DELETE,