semvec/pypi-packages huggingface dataset:
senginta 0.0.3.0
All in one Search Engine for used by API or Python Module (Unofficial)
Requires Python: >=3.8

<p align="center">
    <img src="Senginta.jpg"></img>
</p>

<p align="center">
    All in one Search Engine Scrapper for used by API or Python Module.
</p>

<p align="center">
    <a href="https://youtu.be/-B3CO467Kzo"> How to use: Video</a>
</p>

**`Documentation`** |
------------------- |
[![Documentation](https://img.shields.io/badge/api-reference-blue.svg)]() |

Senginta is All in one Search Engine Scrapper. With traditional scrapping, 
Senginta can be powerful to get result from any Search Engine, and convert
to Json. Now support only for Google Product Search Engine (GShop, GVideo 
and many too) and Baidu Search Engine.

Senginta was originally developed by me alone. So, if you want to contribute for
support another search engine, let's fork this Repository. 

Senginta provides beta Python.

## Install

```
$ pip install senginta
```

To update senginta to the latest version, add `--upgrade` flag to the above
commands.

#### Try your first Senginta program

```shell
$ python
```

```python
>>> from senginta.static.Google import GSearch
>>> search_spider = GSearch('study from home')
>>> print(search_spider.to_json())
...
...
...
Json Formatting
>>> search_spider.get_all()
...
...
...
Dictionary
```

## Resources

*   https://www.naufalardhani.com/2021/05/senginta-all-in-one-search-engine.html
*   Let's contribute your blog about this module here!

## License

[MIT License](LICENSE)
yaast-dynnamitt 0.0.4
AWS credentials MFA-Resolver tool
Requires Python: >=3.6

# Yaast (Jåst)
## YetAnotherAWSSessionTool

*Why?* ..After obtaining a normal accessKey set, 
the MFA enabled user faces the challege of 
mantaining a daily set of temp accessKeys+token (session) for
use with awscli, sdks and the stuff like terraform.

## 0. Setup "start" profile

    aws configure --profile awsops
    # PASTE keys from aws csv file ...
    
    vim ~/.aws/config 
    # ADD mfa_serial = arn:aws:iam::0000000:xxx/xxxxxxx

## 1. write_session (MFA resolver)

Writes a new [default] section into your $HOME/.aws/credentials,
after downloading a new SESSION temp access/token set through a "start" profile.
Start profile name defaults to [awsops] and should have 'mfa_serial' set, together with accesskeys.

Both the *start* and *dest* profiles names can be selected with flags

    ./write_session.py --help


*DEPENDS* on botocore (pip3 install botocore)

## 2. assume+console 

Downloads AssumeRole temp access/token set and will
also mix in a CONSOLE_URL signed with these fresh credentials.

Make sure that you added atleast one profile in $HOME/.aws/config that
contains the `role_arn` attributte .

### 2.1. Shell version

Posix version (/bin/sh #no-bashisms) 

     ./assume+console.sh [role_arn-profile] [json|text]

Format output : "json" is almost what aws-api returns, "text" is a bash script snippet env/export lines 
     
*DEPENDS* on awscli , jq and curl

### 2.2. python3 version

Should only have botocore as single dependency 

PENDING 


## 3. Addind new profiles into $HOME/.aws/config

PENDING

Create multiple profiles from a cfg data file.

### 3.1. cfg file format

Format from basefarm/aws-session-tool , ( REGION is an "extension" )

```
<ROLEID> <ROLEARN>  <NAME>  <EXTID> <REGION>
```

Check sample file _____ .

### 3.2. adding

PENDING

A profile (in ~/.aws/config) will be added with name = `<NAME>`
and adding a 'source_profile' attr to connect into the above session token/credentials.

The 'source_profile' value will be litteraly 'default' if not given with flag.

Currently the only inheritance from the source profile is accesskeys/token so that is 
why we need to set region again here.


```read multiple records from STDIN
add_roles [-s source_profile] < roles.cfg
```
```single operation
add_a_role -n <NAME> -r <ROLEARN> -e <EXTID> -r <REGION> [-s source_profile]
```
TODO: Should `<ROLEID>` be use aswell , session_name perhaps?
TODO: Figure out if -o / overwrite warning should kick in


## 4. Shell aliases 

PENDING

Either `aws --profile x` or `AWS_PROFILE=x` could be put into A AUTOGENERATED SET of aliases
by sourcing a this python script into your ~/.zshrc or ~/.bashrc file.

bla bla