Saravanan666/pypi-org huggingface dataset:
Package: aws-org-client
aws_org_clientContentsOverviewExample UsageDevelopmentOverviewThis project is a python package, aimed at providing a simple interface with AWS
organisation & identity services.Using boto3 clients:identitystoreorganizationssso-adminExample UsageSetup boto session & initialise organisations client to list accounts.importboto3fromaws_org_client.organizationsimportOrganizationssession=boto3.Session(profile_name='my_profile',region_name='my_region')client=Organizations()client.list_accounts()Example response:[{"Id":"string","Arn":"string","Email":"string","Name":"string","Status":"ACTIVE","JoinedMethod":"CREATED","JoinedTimestamp":datetime.datetime(1970,1,1,00,00,00,000000,tzinfo=tzlocal())}]DevelopmentRequirementsInstallpython poetry.You will need a working aws profile configured in your filesystem.SetupInitialise a poetry environment:poetryshellInstall dependencies:poetryinstallProject processesCoverage reportrun coverage report:poetryruncoveragerun-m--source=aws_org_clientpytesttestspoetryruncoveragereportLintingrun pylint with:poetryrunpylintaws_org_clientpoetryrunpylinttestsFormattingrun black formatter with:poetryrunblack.SASTrun bandit scanner:poetryrunbandit.Documentationthis project uses sphinx to produce a static html site; published to
github pages.github actions takes care of building the site & publishing it.to update the files used to build documentation use:poetryrunsphinx-apidoc--ext-autodoc-f-odocs.include any changes to the docs directoryBuild Documentation locallyyou may wish to build documentation locally before publishing it.form the project root run:poetryrunsphinx-builddocs_buildthis will create directory_buildin the project root where you can load
html in your browser.
Package: aws-orgs
A configuration management tool set for AWS Organizations.Full documentation is available athttps://aws-orgs.readthedocs.io/en/latestFeaturesEnsure state of AWS Organizations and IAM resourses peryamlformatted
specification files.Configure AWS Organizations resources:organizational unitsservice control policiesaccount creation and organizational unit placementCentrally manage IAM access across AWS Organization accounts:IAM users/groups in a centralAuthaccountcustomer managed IAM policiesIAM roles and trust delegation in organization accountsInstallationPython virtual environment (recommended):source ~/path_to_my_venv/bin/activate
pip install aws-orgsEditable copy in venv:git clone https://github.com/ucopacme/aws-orgs
pip install -e aws-orgs/Uninstall:pip uninstall aws-orgsConfiguration quick startRun theawsorgs-spec-initscript to generate an initial set of spec-files:awsorgs-spec-initThis generates an initialconfig.yamlspec files under~/.awsorgs.  Edit
these as needed to suit your environment.See--helpoption for full usage.Console Scriptsaws-orgsprovides the following python executibles:awsorgsManage recources in an AWS Organization.awsaccountsManage accounts in an AWS Organization.awsauthManage users, group, and roles for cross account access in an
AWS Organization.awsloginprofileManage AWS IAM user login profile.All commands execute indry-runmode by default.  Include the--execflag to affect change to AWS resources.  Run each of these with the ‘–help’
option for usage documentation.awsorgs report
awsorgs organization
awsorgs organization --exec

awsaccounts report
awsaccounts create [--exec]
awsaccounts alias [--exec]

awsaccounts invite --account-id ID [--exec]
# from invited account:
awsorgs-accessrole --master_id ID [--exec]

awsauth report
awsauth report --users
awsauth report --delegations
awsauth report --credentials --full
awsauth report --account ucpath-prod --users --full

awsauth users [--exec]
awsauth delegations [--exec]
awsauth local-users [--exec]

awsloginprofile maryanne
awsloginprofile maryanne --new
awsloginprofile maryanne --reset
awsloginprofile maryanne --disable-expired --opt-ttl 48Author:Ashley Gould (agould@ucop.edu)Version:0.3.1
Package: aws-org-tree
aws-org-treePrints a text tree representation of an AWS organization.aws-org-treeRoot (r-p74l)
├── isme-root-zcskbx (039444814027)
├── Sandbox (ou-p74l-a2llanp8)
└── Security (ou-p74l-094nw8v7)
    ├── Log Archive (386884128156)
    └── Audit (466721047587)Use the--node-name-formatoption to print different properties of the resources. This part doesn't work well yet because different resources have different properties. If the property is missing the property name is used as a placeholder.poetryrunaws-org-tree--node-name-format"{Type} {Email}"ROOT Email
├── ACCOUNT iain+awsroot+zcskbx@isme.es
├── ORGANIZATIONAL_UNIT Email
└── ORGANIZATIONAL_UNIT Email
    ├── ACCOUNT iain+awsroot+zcskbx+log-archive@isme.es
    └── ACCOUNT iain+awsroot+zcskbx+audit@isme.esOther formatsI removed the JSON tree (json-tree) and flat JSON formats (json-flat) formats Useversion0.2.0if you need those.DevelopmentInstall Python 3.8.InstallPoetryviaPipx.Clone the repo.Runpoetry install.Hack away.Run quality checks withpoetry run pre-commit run --all-files.Install quality checks aspre-commit checkswithpoetry run pre-commit install.Continuous integrationPush to the main branch to run the development quality checks via GitHub Actions.Run continuous integration locally withact.
Package: aws_ork
A Python daemon to sign and remove Salt minion keys for instances being
spawned or terminated via Auto Scaling groups (ASGs).The ASG sends messages for launch and termination events via SNS to
SQS. The daemon is listening to the SQS messages and:- removes Salt minion keys on termination messages- accepts minion keys matching the instance-id in the launch messagesIf an S3 URL is configured, the content of/etc/salt/pkigets synced
to S3.Building / TestsCan be used as is or packaged viasetuptools,setup.pyetc.In order run tests and verify running on mutiple versions of Python use:toxIf successful it should look something like this:flake8: commands succeeded
py27: commands succeeded
py34: commands succeeded
congratulations :)InstallationPyPipip install aws_orklocal dev versionYou can find a pip compatible zip file in.tox/dist, which you can
install via:pip install .tox/dist/aws_ork-<VERSION>.zipUsageusage: aws_ork [-h] [-v] [-d] [--syslog] [--purge]

Listens to an SQS queue and accepts and removes Salt minion keys

optional arguments:
  -h, --help     show this help message and exit
  -v, --verbose  Enable debug logging
  -d, --daemon   Daemonize and enable logging to file
  --syslog       Log to syslog rather than file, only in daemon mode
  --purge        Purge all message from queue at startupConfig FileThe daemon looks for an optional config file in/etc, see:data/aws_ork.confOptionsOptionDefaultSQS_Region"us-west-2"QueueName"SaltMasterTestQueue"PollPause0BucketUrlNoneBucketRegionNoneDeleteUnknownMessagesTrueUnix serviceExample SysV style init file provided, see:data/sys_init/aws_orkExample SystemD style config, see:data/systemd/*FAQWhere is this daemon supposed to run?The daemon is supposed to run on the Salt master instance as it
requires file system access to the Salt master’s keystore.Why is ``/etc/salt/pki`` backed up to S3?Normally the Salt master instance uses a storage type that is not
persistent (e.g. EBS). Therefore, the keystore is synced to S3 on
each change in order to be restored during boot in case the Salt
master instance needs to replaced (not covered by this service).What does the PollPause option do ?AWS charges each request to SQS. AWS Ork already uses long polling,
but if some delayed processing is acceptable, pausing between read
requests can further reduces costs.Using the default value of “0” (no pause):( 365*24*3600 ) / 20 * 0.0000004 $ = 0.63$ / yearWho should have access to the S3 location?As the key store contains private keys which could be used to
impersonate Salt minions, download configuration data and potentially
passwords for other services, access should be limited accordingly.
Package: awsovpn
awsovpnManage an OpenVPN instance in your private EC2 cloud using this script.UsageCreate an OpenVPN EC2 instance and configure it for VPN access.awsovpnupThen following instructions to configure a Profile and install in your local OpenVPN client.Terminate the OpenVPN EC2 instance and remove all EC2 resources mangaed by this script:awsovpndownInstallpython-mpipinstallawsovpnConfigureConfigure using any of combination of the following methods:awscli configurationIf you haveawscliinstalled and configured, then awsovpn can utilize this same configuration. Just use--profile PROFILEto specify an AWS configuration profile.awsovpn--profilemyprofileupenvironment variablesCreate a.envfile or set the following environment variables:AWS_REGION=
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_PROFILE=use argumentsYou can also pass credential configuration as arguments:e.g.awsovpn--regionREGION--access-key-idACCESS_KEY_ID--secret-access-keySECRET_ACCESS_KEY
Package: aws-parallelcluster
AWS ParallelCluster is an AWS supported Open Source cluster management tool that makes it easy for you to deploy and
manage High Performance Computing (HPC) clusters in the AWS cloud.
Built on the Open Source CfnCluster project, AWS ParallelCluster enables you to quickly build an HPC compute environment in AWS.
It automatically sets up the required compute resources and a shared filesystem and offers a variety of batch schedulers such as AWS Batch and Slurm.
AWS ParallelCluster facilitates both quick start proof of concepts (POCs) and production deployments.
You can build higher level workflows, such as a Genomics portal that automates the entire DNA sequencing workflow, on top of AWS ParallelCluster.Documentation can be found athttps://docs.aws.amazon.com/parallelcluster/
Package: aws-parameter-store
aws-parameter-storeAWS SSM parameter store client that constructs nested dictionary out of hierarchical pathFeaturesGets parameters by pathCollects all paged results automaticallyLightweightInstallationInstall withpip:pip install aws-parameter-storeGetting startedImport the module and create a new instance ofAwsParameterStore.fromaws_parameter_storeimportAwsParameterStorestore=AwsParameterStore('us-east-1')APIoverviewBy defaultJSON parameters are being evaluatedParameters are decryptedExamplesGiven the parameters:NameValuekey-awrongexample/key-bflatexample/key-csecretexample/path1/path2/key-ddeepret=store.get_parameters_dict('/example/')assertret=={'key-b':'flat','key-c':'secret','path1':{'path2':{'key-d':'deep'}}}RequirementsPython3.6+ContributingYou are welcome to contribute and join our family =)TestingThis projects testing uses pytest. Simply test by runningpytestLicenseSee theLICENSEfile for license rights and limitations (Apache License, Version 2.0)
Package: aws-paramstore-py
Query params from AWS System Manager Parameter StoreInstallpipinstallaws-paramstore-pyUsagein shell# AWS credentials from env varsaws-pspy/path/to/params# returns {"key1": "value1", "key2": "value2"}eval"$(aws-pspy/path/to/params--bash-export)"# set env vars:
# - key1="value1"
# - key2="value2"in Pythonimportaws_paramstore_pyasparamstore# use default boto3 ssm clientparams=paramstore.get('/path/to/params')# dict(key1: "value1", key2: "value2")# use your own boto3 ssm clientimportboto3ssm=boto3.client('ssm')params=paramstore.get('/path/to/params',ssm_client=ssm)
Package: aws-parquet
aws-parquetaws-parquetis a toolkit than enables working with parquet datasets on AWS. It handles AWS S3 reads/writes, AWS Glue catalog updates and AWS Athena queries by providing a simple and intuitive interface.MotivationThe goal is to provide a simple and intuitive interface to create and manage parquet datasets on AWS.aws-parquetmakes use of the following tools:awswrangleras an AWS SDK for pandaspanderafor pandas-based data validationtypeguardandpydanticfor runtime type checkingFeaturesaws-parquetprovides aParquetDatasetclass that enables the following operations:create a parquet dataset that will get registered in AWS Glueappend new data to the dataset and update the AWS Glue catalogread a partition of the dataset and perform proper schema validation and type castingoverwrite data in the dataset after performing proper schema validation and type castingdelete a partition of the dataset and update the AWS Glue catalogquery the dataset using AWS AthenaHow to setupUsing pip:pipinstallaws_parquetHow to useCreate a parquet dataset that will get registered in AWS Glueimportosfromaws_parquetimportParquetDatasetimportpandasaspdimportpanderaaspafrompandera.typingimportSeries# define your pandera schema modelclassMyDatasetSchemaModel(pa.SchemaModel):col1:Series[int]=pa.Field(nullable=False,ge=0,lt=10)col2:Series[pa.DateTime]col3:Series[float]# configurationdatabase="default"bucket_name=os.environ["AWS_S3_BUCKET"]table_name="foo_bar"path=f"s3://{bucket_name}/{table_name}/"partition_cols=["col1","col2"]schema=MyDatasetSchemaModel.to_schema()# create the datasetdataset=ParquetDataset(database=database,table=table_name,partition_cols=partition_cols,path=path,pandera_schema=schema,)dataset.create()Append new data to the datasetdf=pd.DataFrame({"col1":[1,2,3],"col2":["2021-01-01","2021-01-02","2021-01-03"],"col3":[1.0,2.0,3.0]})dataset.update(df)Read a partition of the datasetdf=dataset.read({"col2":"2021-01-01"})Overwrite data in the datasetdf_overwrite=pd.DataFrame({"col1":[1,2,3],"col2":["2021-01-01","2021-01-02","2021-01-03"],"col3":[4.0,5.0,6.0]})dataset.update(df_overwrite,overwrite=True)Query the dataset using AWS Athenadf=dataset.query("SELECT col1 FROM foo_bar")Delete a partition of the datasetdataset.delete({"col1":1,"col2":"2021-01-01"})Delete the dataset in its entiretydataset.delete()
Package: aws-parsecf
(Tries to) parse AWS CloudFormation’s intrinsic functions in the
template.Quick StartFirst, install the library:pipinstallaws-parsecfThen, from a Python interpreter:importaws_parsecfwithopen('/path/to/cloudformation.json','r')asf:print(aws_parsecf.load_json(f))Notethat some of the intrinsic functions require a configured
environment (like"Fn::GetAZs"), so if you don’t have it set:awsconfigureUsage3 simple methods:aws_parsecf.load_json(stream,region)aws_parsecf.loads_json(string,region)aws_parsecf.load_yaml(stream_or_string,region)regionis optional, and defaults to the region you specified when usingaws configure. If you didn’t specify a default region inaws configure, or you want to override it, you should specify your
region:aws_parsecf.load_json(stream,region='us-west-1')If your stack is parameterized, the default values will be used along with
possibly supplying parameters:aws_parsecf.load_json(stream,region,{'DomainName':"aws.parsecf.com"})ContributingRunning tests:./setup.pytestMissing pieces:Support YAML short form.You know the drill, PR!
Package: aws-pcluster-bootstrap-helpers
# aws_pcluster_bootstrap_helpers[![image](https://img.shields.io/pypi/v/aws_pcluster_bootstrap_helpers.svg)](https://pypi.python.org/pypi/aws_pcluster_bootstrap_helpers)[![image](https://img.shields.io/travis/dabble-of-devops-bioanalyze/aws_pcluster_bootstrap_helpers.svg)](https://travis-ci.com/dabble-of-devops-bioanalyze/aws_pcluster_bootstrap_helpers)Helpers to bootstrap a AWS PCluster + SLURM + Custom AMIsFree software: Apache Software License 2.0## FeaturesBuild a PCluster AMI and watch itBuild a PCluster ClusterPlease note that you must build new AMIs per version of parallel cluster and region.## CreditsThis package was created with
[Cookiecutter](https://github.com/audreyr/cookiecutter) and the
[audreyr/cookiecutter-pypackage](https://github.com/audreyr/cookiecutter-pypackage)
project template.History0.1.0 (2022-08-11)First release on PyPI.
Package: aws-pcluster-dask-gateway
aws_pcluster_dask_gatewayiA helper function to configure Dask Gateway to play nice with AWS PClusterFree software: Apache Software License 2.0Documentation:https://aws-pcluster-dask-gateway.readthedocs.io.FeaturesAutomatically parses parallelcluster’s config files to generate a dask-gateway template.Uses the jupyterhub-kubernetes profiles to list CPU/GPUCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2022-06-24)First release on PyPI.
Package: aws-pcluster-helpers
AWS PCluster HelpersHelpers to generate different configurations for PClusterInstallation$pipinstallaws_pcluster_helpersQuickStartPrint help$pcluster-helper--helpPrint sinfo table$pcluster-helpersinfoPrint nextflow slurm config to stdout$pcluster-helpergen-nxf-slurm-config--stdoutFree software: Apache Software License 2.0Documentation:https://aws-pcluster-helpers.readthedocs.io.FeaturesTODOCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2022-05-26)First release on PyPI.
Package: aws-pcluster-slurm-spawner
AwsPClusterSlurmSpawnerExtend Jupyterhub’s BatchSpawner to deal with AWS ParallelCluster’s SLURM environmentFree software: Apache Software License 2.0Documentation:https://aws-pcluster-slurm-spawner.readthedocs.io.FeaturesTODOCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2022-05-15)First release on PyPI.
Package: aws-pdk
AWS PDKAll documentation is located at:https://aws.github.io/aws-pdkaws-archPlease refer toDeveloper Guide.cdk-graphPlease refer toDeveloper Guide.cdk-graph-plugin-diagramPlease refer toDeveloper Guide.cdk-graph-plugin-threat-composerPlease refer toDeveloper Guide.cloudscape-react-ts-websitePlease refer toDeveloper Guide.identityPlease refer toDeveloper Guide.infrastructurePlease refer toDeveloper Guide.monorepoPlease refer toDeveloper Guide.pdk-nagPlease refer toDeveloper Guide.pipelinePlease refer toDeveloper Guide.static-websitePlease refer toDeveloper Guide.type-safe-apiPlease refer toDeveloper Guide.
Package: awspice
Table of content (Full doc inReadTheDocs) :InstallationConfigurationTestUsageWhat is Awspice?Is a wrapper of Boto3 library to list inventory and manage your AWS infrastructure
The objective of the wrapper is to make easier some common tasks in AWS, being able to dig through different regions and accounts.Awspice make it easy to:List all your EC2 instances for multiple regions and accountsGet deployed infraestructure behind a Load Balancer.List all instances with exposed critical ports like 22 or 3389Get info about all certificates of your account/sFind exposed S3 bucketsInstallationpipinstallawspiceConfigurationThe client is built and configured usingawspice.connect(). This method indicates the type of authentication and region on which you are going to work.importawspice# Region: eu-west-1 | Profile: Defaultaws=awspice.connect()# Using profilesaws=awspice.connect(region='us-west-2',profile='dev_profile')# Using access keysaws=awspice.connect('us-west-2',access_key='AKIA***********',secret_key='/HR$4************')UsageExample: Get balancer and instances behind a domain.aws=awspice.connect()elb=aws.service.elb.get_loadbalancer_by('domain','donalddumb.com')forelb_instanceinelb['Instances']:instance=aws.service.ec2.get_instance_by('id',elb_instance['InstanceId'])Example: List all unused volumesall_regions=aws.service.ec2.get_regions()volumes=awsmanager.service.ec2.get_volumes_by('status','available',regions=all_regions)Example: Search instance in all accounts and regions by Public IPprofiles=aws.service.ec2.get_profiles()regions=aws.service.ec2.get_regions()forprofileinprofiles:aws.service.ec2.change_profile(profile)instance=aws.service.ec2.get_instance_by('publicip','35.158.163.235',regions=regions)ifinstance:print'Instance found:%s(Account:%s, Region:%s)'%(instance['InstanceId'],instance['RegionName'],instance['Authorization']['Value'])break
Package: aws-pipeline-creator
AWS Codepipeline CreatorFeaturesaws-pipeline-creator creates a aws codepipeline cloudformation stack,
and points to a build specifical file in the code repositoryInstallationaws-pipeline-creator is on PyPI so all you need is:$ pip install aws-pipeline-creatorExampleGetting help$ pipeline-creator upsert --help
Usage: pipeline-creator upsert [OPTIONS]

   primary function for creating a bucket :return:

 Options:
   -v, --version TEXT  code version
   -d, --dryrun        dry run
   -y, --yaml          YAML template (deprecated - YAMLness is now detected at
                       run-time
   --no-poll           Start the stack work but do not poll
   -i, --ini TEXT      INI file with needed information  [required]
   --debug             Turn on debugging
   --help              Show this message and exit.

pipeline-creator upsert -i config/my.iniExample Ini file[environment]
# This is a general bucket where the cloudformation template will be uploaded to prior to deployment
bucket = cloudformation-templates
# The name you want on the cloudformation stack
stack_name = my-stack-name
region = us-east-1
profile = my-aws-profile


[tags]
# These are the tags which will be automatically applied to resources
Name = test-codepipeline
ResourceOwner = my_boss
Project = MyCoolProject
DeployedBy = me

[parameters]
# CodeCommit repository name
RepositoryName = repo_name
# Codecommit repository branch name
RepositoryBranchName = master
# A project name or code
Project = test
ProjectDescription =  test
# The role which is utilized for the code pipeline, see below for an example role policy
BuildServiceRole = arn:aws:iam::123456789:role/AWSCodebuildRole
BuildProjectName = MyBuild
Subnets = subnet-c1234556
SecurityGroups = sg-123456
Timeout = 60
# The location in the repository where the build spec file is located
BuildspecFile = folder/buildspec.yml
# Set the environment code.  This is how developers code deployments in the build spec.
# If EnvCode = dev, then do this, if EnvCode is prod, then do that
EnvironmentCode = dev
VpcId = vpc-123456
# This is a bucket where the builds from each stage in the build process are stored
DeploymentBucketName = codepipeline-deployments
# The image to utilize
# You can also use default AWS images from https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html
# Example: Image = aws/codebuild/docker:17.09.0
Image = 123456789.dkr.ecr.us-east-1.amazonaws.com/codepipeline:latest


[meta-parameters]
# These are the metadata parameters which are applied to the template via jinja2
ProjectName = myprojectDemonstration
Package: aws-plugin-bucket-policy
aws-plugin-bucket-policyAWS CLI plugin - bucket policy admin toolInstallationDependencies: python3-minimal python3-pip mandoc groff-base
optionally: python3-venvOptionally start virtualenv:python3 -m venv venv; . venv/bin/activatepip install --upgrade pip setuptools awscli aws-plugin-bucket-policyConfigurationaws config.aws/config:[plugins]s3bucket-policy=aws_plugin_bucket_policyS3 credentials:.aws/credentials:[default]aws_access_key_id=***aws_secret_access_key=***or using environment variables: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY \HelpFor help runaws s3bucket-policy helporaws s3bucket-policy SUBCOMMAND helpPlugin commands manual on GitHubExamples:awss3bucket-policy--profilePROFILE_NAMEget-policy--bucketBUCKET_NAMEawss3bucket-policy--profilePROFILE_NAMEnew-policy--bucketBUCKET_NAME--newpol-typeshare-w-user--newpol-spectenant=TENANT_NAME,user=USER_NAME,action=rwawss3bucket-policy--profilePROFILE_NAMEnew-policy--bucketBUCKET_NAME--newpol-typeshare-w-tenant--newpol-spectenant=TENANT_NAME,action=roawss3bucket-policy--profilePROFILE_NAMEnew-policy--bucketBUCKET_NAME--newpol-typero-publicawss3bucket-policy--profilePROFILE_NAMEput-policy--bucketBUCKET_NAME--policyPOLICY_FILE.jsonawss3bucket-policy--profilePROFILE_NAMEdelete-policy--bucketBUCKET_NAMEDocker way:Dockerfilebased on ubuntu:jammyS3 credentials should be defined inS3_envas AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables:
(seeS3_env.templatefile)AWS_ACCESS_KEY_ID=***AWS_SECRET_ACCESS_KEY=***Usage examples:dockerbuild-ts3bucket-policy.dockerrun-it--rm-uawscli--env-file=S3_env--names3bucket-policys3bucket-policy--endpointENDPOINT_URLget-policy--bucketBUCKET_NAMEdockerrun-it--rm-uawscli--env-file=S3_env--names3bucket-policys3bucket-policy--endpointENDPOINT_URLhelpdockerrun-it--rm-uawscli--env-file=S3_env--names3bucket-policys3bucket-policy--endpointENDPOINT_URLnew-policyhelpdockerrun-it--rm-uawscli--env-file=S3_env--names3bucket-policys3bucket-policy--endpointENDPOINT_URLnew-policy--bucketBUCKET_NAME--newpol-typeshare-w-tenant--newpol-spectenant=TENANT_NAME,action=ro