
Research
Security News
Malicious PyPI Package Exploits Deezer API for Coordinated Music Piracy
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
@adobe/aio-cli-plugin-cloudmanager
Advanced tools
Cloud Manager Plugin for the Adobe I/O CLI
$ aio plugin:install @adobe/aio-cli-plugin-cloudmanager
At minimum, an integration must be created in the Adobe I/O Console which has the Cloud Manager service. You may also add other services to this integration if you want to use other Adobe I/O CLI plugins. For example, to use the Console Plugin, your integration needs to have the "I/O Management API" service.
After you've created the integration, create a config.json
file on your computer and navigate to the integration Overview page. From this page, copy the client_id
and client_secret
values to the config file; if you navigate to the JWT tab in Console, you'll get the value for the jwt_payload
.
//config.json
{
"client_id": "value from your CLI integration (String)",
"client_secret": "value from your CLI integration (String)",
"jwt_payload": { value from your CLI integration (JSON Object Literal) },
"token_exchange_url": "https://ims-na1.adobelogin.com/ims/exchange/jwt",
"console_get_orgs_url":"https://api.adobe.io/console/organizations",
"console_get_namespaces_url":"https://api.adobe.io/runtime/admin/namespaces/"
}
The last bit you need to have at hand is the private certificate you've used to create the integration; you need the private key, not the public one. Now, you are ready to configure the aio
CLI.
First, configure the credentials:
aio config:set jwt-auth PATH_TO_CONFIG_JSON_FILE --file --mime-type=application/json
Then, configure the private certificate:
aio config:set jwt-auth.jwt_private_key PATH_TO_PRIVATE_KEY_FILE --file --mime-type=application/x-pem-file
If you want to avoid passing the program ID flag repeatedly, you can configure it using:
$ aio config:set cloudmanager_programid PROGRAMID
For example
$ aio config:set cloudmanager_programid 4
./bin/run cloudmanager:get-current-execution PIPELINEID
./bin/run cloudmanager:get-quality-gate-results PIPELINEID EXECUTIONID ACTION
./bin/run cloudmanager:list-current-executions
./bin/run cloudmanager:list-pipelines
./bin/run cloudmanager:list-programs
./bin/run cloudmanager:start-execution PIPELINEID
./bin/run cloudmanager:get-current-execution PIPELINEID
get pipeline execution
USAGE
$ ./bin/run cloudmanager:get-current-execution PIPELINEID
ARGUMENTS
PIPELINEID the pipeline id
OPTIONS
-p, --programId=programId the programId. if not specified, defaults to 'cloudmanager_programid' config value
-r, --passphrase=passphrase the passphrase for the private-key
See code: src/commands/cloudmanager/get-current-execution.js
./bin/run cloudmanager:get-quality-gate-results PIPELINEID EXECUTIONID ACTION
get quality gate results
USAGE
$ ./bin/run cloudmanager:get-quality-gate-results PIPELINEID EXECUTIONID ACTION
ARGUMENTS
PIPELINEID the pipeline id
EXECUTIONID the execution id
ACTION (codeQuality|security|performance) the step action
OPTIONS
-p, --programId=programId the programId. if not specified, defaults to 'cloudmanager_programid' config value
-r, --passphrase=passphrase the passphrase for the private-key
See code: src/commands/cloudmanager/get-quality-gate-results.js
./bin/run cloudmanager:list-current-executions
list running pipeline executions
USAGE
$ ./bin/run cloudmanager:list-current-executions
OPTIONS
-p, --programId=programId the programId. if not specified, defaults to 'cloudmanager_programid' config value
-r, --passphrase=passphrase the passphrase for the private-key
See code: src/commands/cloudmanager/list-current-executions.js
./bin/run cloudmanager:list-pipelines
lists pipelines available in a Cloud Manager program
USAGE
$ ./bin/run cloudmanager:list-pipelines
OPTIONS
-p, --programId=programId the programId. if not specified, defaults to 'cloudmanager_programid' config value
-r, --passphrase=passphrase the passphrase for the private-key
See code: src/commands/cloudmanager/list-pipelines.js
./bin/run cloudmanager:list-programs
lists programs available in Cloud Manager
USAGE
$ ./bin/run cloudmanager:list-programs
OPTIONS
-e, --enabledonly only output Cloud Manager-enabled programs
-r, --passphrase=passphrase the passphrase for the private-key
See code: src/commands/cloudmanager/list-programs.js
./bin/run cloudmanager:start-execution PIPELINEID
start pipeline execution
USAGE
$ ./bin/run cloudmanager:start-execution PIPELINEID
ARGUMENTS
PIPELINEID the pipeline id
OPTIONS
-p, --programId=programId the programId. if not specified, defaults to 'cloudmanager_programid' config value
-r, --passphrase=passphrase the passphrase for the private-key
0.0.2 (04/06/2019)
No changelog for this release.
FAQs
Cloud Manager commands for the Adobe I/O CLI
The npm package @adobe/aio-cli-plugin-cloudmanager receives a total of 1,674 weekly downloads. As such, @adobe/aio-cli-plugin-cloudmanager popularity was classified as popular.
We found that @adobe/aio-cli-plugin-cloudmanager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.
Security News
Newly introduced telemetry in devenv 1.4 sparked a backlash over privacy concerns, leading to the removal of its AI-powered feature after strong community pushback.