You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have a Pipes user report of an issue where after installing multiple mods (AWS/Azure/GCP compliance) and all 3 mod installations returning no error, when we then try to list mod variables for the Pipes workspace we get an error.
Error loading input variables","error":"Bad Request: not all dependencies are installed - run 'powerpipe mod install'
Powerpipe version (powerpipe -v)
Example: v1.0.1 / v1.1.0
To reproduce
These are the steps the user takes via the API:
Create a Pipes workspace
When workspace state is enabled, create aws, azure and gcp connections
When connections are installed, install AWS/Azure/GCP compliance mods one at a time - wait for a state of installed before moving to the next
When all mod installs show installed, create a pipeline that depends on
Trigger pipelines
Install these three mods one.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
We have a Pipes user report of an issue where after installing multiple mods (AWS/Azure/GCP compliance) and all 3 mod installations returning no error, when we then try to list mod variables for the Pipes workspace we get an error.
Error loading input variables","error":"Bad Request: not all dependencies are installed - run 'powerpipe mod install'
Powerpipe version (
powerpipe -v
)Example: v1.0.1 / v1.1.0
To reproduce
These are the steps the user takes via the API:
enabled
, createaws
,azure
andgcp
connectionsinstalled
before moving to the nextinstalled
, create a pipeline that depends onExpected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: