Expected Behaviour

Plugin should install without warnings

Actual Behaviour

warning "@adobe/aio-cli-plugin-cloudmanager > @oclif/[email protected]" has unmet peer dependency "@oclif/plugin-help@^2".
warning @adobe/aio-cli-plugin-cloudmanager > @adobe/[email protected]: WARNING: This module has been renamed to @adobe/aio-lib-core-config. Please install it instead. See https://github.com/adobe/aio-lib-core-config for more information.

Reproduce Scenario (including but not limited to)

Don't have the plugin installed

Steps to Reproduce

Install the plugin

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

When a deployment is paused, cancelling it needs to be done via the advance endpoint.

Actual Behaviour

Wrong endpoint is used

Reproduce Scenario (including but not limited to)

Have a paused deployment step

Steps to Reproduce

Invoke cancel-current-execution

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The dependency @adobe/aio-cli-plugin-runtime was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-cli-plugin-runtime is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

When running aio (without any command) the description for the cloudmanager plugin should be informative.

Actual Behaviour

it isn't :)

  cloudmanager  get pipeline execution

Reproduce Scenario (including but not limited to)

Steps to Reproduce

1. Install plugin
2. Run aio

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Secrets should be output the same way in cloudmanager:list-environment-variables and cloudmanager:set-environment-variables

Actual Behaviour

Secret values are output as undefined

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The dependency @adobe/aio-lib-core-config was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/aio-lib-core-config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

The README should contain runnable commands.

Actual Behaviour

It contains cloudmanager:base-environment-variables-command which is a base class, not intended to be used directly

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Look at the README :)

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Tests should pass

Actual Behaviour

Tests are failing

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

When the API response contains an error message and code, it would be helpful if that information was shown in the CLI output.

Actual Behaviour

Only the HTTP response code and status are displayed.

Expected Behaviour

$ aio cloudmanager

should output complete help

Actual Behaviour

Missing some recently added commands

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

$ aio cloudmanager:delete-pipeline PIPELINEID

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

cloudmanager:get-quality-gate-results should accept contentAudit and experienceAudit as parameters and show the metrics for this step.

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Cloud Manager will shortly support pipeline variables, similar to environment variables. This should be available in the CLI.

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The dependency @oclif/plugin-help was updated from 2.2.2 to 2.2.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@oclif/plugin-help is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

just a convenience feature, in the cloud manager UI the environment ids show with an "e" prefix, allowing the e as prefix to be passed in would be nice

Created from #135

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

$ aio cloudmanager:set-environment-variables 12345 --secret MY_VAR2 "some secret value"
$ aio cloudmanager:set-environment-variables 12345 --delete MY_VAR2

should result in the environment variable being deleted

Actual Behaviour

setting variables... !
Error: Cannot set variables: https://cloudmanager.adobe.io/api/program/54321/environment/12345/variables (400 Bad Request)
    at res.text.then.text (~/workspaces/projects/aio-cli-plugin-cloudmanager/src/client.js:60:39)

Reproduce Scenario (including but not limited to)

Have a Cloud Service program and environment and an integration with the Deployment Manager role

Steps to Reproduce

See above

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Some steps (primarily the code quality step) support alternate log files. The get-execution-step-logs command should support this.

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

The Delete Environment API is available, but not used in the CLI

Actual Behaviour

There should be a delete-environment command.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

There should be commands to cancel/reject or advance/approve the current execution.

Expected Behaviour

When starting an execution, the execution id should be output on the CLI

Actual Behaviour

It isn't.

Reproduce Scenario (including but not limited to)

You have an idle pipeline

Steps to Reproduce

run aio cloudmanager:start-execution PIPELINEID

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

If you want this functionality, please add aiojbot to your repo under Settings -> Manage Access under a Triage role. Thanks.

The sync functionality runs every 15 minutes, and will watch for label events in issues. (bug, enhancement, question, feature)

Expected Behaviour

This plugin should not have a dependency on aio-cli-plugin-runtime

Actual Behaviour

It does.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Something like

$ aio cloudmanager:get-execution-step-details PIPELINEID EXECUTIONID

and return a table of the steps within the execution -- start times, end times, durations

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The dependency cli-ux was updated from 5.4.0 to 5.4.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cli-ux is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Expected Behaviour

CLI should have a cloudmanager:delete-program command

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

There's no reason to be supporting node 8 anymore. Everyone should be on node 10 or higher.

Actual Behaviour

node 8 is tested.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

see #37

Logs taken while reproducing problem

Would it be possible to add a command to check for a new available update in general or for an environment?
Would it then be possible to have an additional command to update an environment if there is an update?

Best
Zubair

Although in the OSGi configuration for PID org.apache.jackrabbit.oak.security.authorization.AuthorizationConfigurationImpl I see the value [administrators, $[env:aemCloudAdministrators;default=administrators]] being set for property administrativePrincipals, the environment variable called aemCloudAdministrators is not listed via aio cloudmanager:list-environment-variables for that particular environment. Still is must have a certain value as all users being member of a cryptic group AEM Administrators-3e6e8bd0a05f39bc82d788bb27ac83b4 are being administrators!

Please make sure that all environment variables are exposed from aio cloudmanager:list-environment-variables (even the ones which may be set as start argument)

The devDependency eslint-plugin-jest was updated from 22.13.0 to 22.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Expected Behaviour

$ aio cloudmanager:update-pipeline --programId=1234 123456 --updateAemBuild

Since Dev environments don't autoupdate, is it possible to get an option for update-pipeline to update to the latest AEM build? It seems that update-pipeline command can only update the git branch attached to the pipeline. This is a nice feature in the UI that would be helpful in this tool.

Expected Behaviour

$ aio cloudmanager:get-execution-step-log PIPELINEID EXECUTIONID ACTION

Should output to stdout by default, but also allow output to a file

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

When a command fails, currently only the status code is output, e.g.

Cannot set variables: https://cloudmanager.adobe.io/api/program/4/environment/11/variables (400 Bad Request)

Although more detailed information is available when DEBUG is enabled, It would be better if this message contained validation errors.

Steps to Reproduce

Run a command that fails

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

When an environment doesn't have a description (which is most of the time), the description column should be blank.

Actual Behaviour

The string undefined is displayed

Reproduce Scenario (including but not limited to)

A program with environments without descriptions (most of them)

Steps to Reproduce

Run aio cloudmanager:list-environments

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

It'd be useful if there was a way to open the developer console for an environment from the CLI.

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

There should be a way to get the quality gate results for a particular execution of a pipeline

The devDependency eslint-plugin-jest was updated from 22.9.0 to 22.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency eslint-plugin-jest was updated from 22.14.1 to 22.15.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

@adobe/aio-cli-plugin-jwt-auth has been deprecated in favor of @adobe/aio-lib-ims.

In order to migrate and achieve a level of backwards compatibility, there must be some migration process from the "old" configuration structure (jwt_auth) to the new one (ims.contexts.CONTEXT_NAME). This migration can be automatically done in an init hook, with the following caveats:

• If there is local config, it should be migrated to local, not global config.
• If there is global config, it should be migrated to global config.
• If the config is passed through environment variables, no migration should be done.

This will still technically be a breaking change since passphrase is not supported (see adobe/aio-lib-ims#52).

However, at this point this is blocking a separate feature request (#198) since if a flag was provided to select an alternate configuration key for the configuration used with @adobe/aio-cli-plugin-jwt-auth migration would not be possible in a fully automated fashion.

Getting an execution by ID is now possible using a newly added HAL link. The old way of hand-building the execution link should be replaced.

The devDependency fetch-mock was updated from 8.2.1 to 8.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

fetch-mock is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Expected Behaviour

$ aio cloudmanager:update-pipeline --branch=develop

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Should be a new command

$ aio cloudmanager:list-environments

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

In the documentation for https://github.com/adobe/aio-cli-plugin-cloudmanager/blob/main/README.md#aio-cloudmanagerdownload-logs-environmentid-service-name-days and https://github.com/adobe/aio-cli-plugin-cloudmanager/blob/main/README.md#aio-cloudmanagertail-log-environmentid-service-name is written "lists available logs for an environment in a Cloud Manager program"

For both commands, this is not really the case. Could you please improve the description?
For people don't have access to a sandbox it would be easier to unterstand.

Expected Behaviour

when running

$ DEBUG=* aio cloudmanager:<anything>

it would be helpful if the debug output included the actual HTTP response body when an error occurred

Actual Behaviour

Debug output only includes fetched URLs

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Best practice now is to have a separate npm module (aio-lib-XXX) which contains the actual API logic and the plugin is just a wrapper around this.

Expected Behaviour

Running

$ aio cloudmanager

should output something (ideally the help message)

Actual Behaviour

Doing this returns an error:

TypeError: this.run is not a function
    at CloudManagerCommand._run (~/.local/share/@adobe/aio-cli/node_modules/@oclif/command/lib/command.js:44:31)

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

When there are no log options, the output should say that.

Actual Behaviour

You just get an empty table.

Reproduce Scenario (including but not limited to)

• You have an environment with no log options

Steps to Reproduce

Invoke aio cloudmanager:list-available-log-options on an environment with no log options

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

There should be an easier way to update a pipeline specifying a tag. While this is currently possible, it's not entirely intuitive.

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

$ npx depcheck
Unused dependencies
* @oclif/config
* @oclif/errors
* @oclif/plugin-help
* zlib
Missing dependencies
* execa: ./e2e/e2e.js
* lodash: ./src/client.js
* @adobe/aio-cli-plugin-config: ./test/fixtures/scripts/global-setup.js

devDep warnings removed because I think they are false positives.