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
There is a TypeInstance with AWS credentials available in the system. It's not used in any Policy and is not passed when creating an Action.
When creating a new Action, for example cap.interface.database.postgresql.install, renderer chooses an Implementation for AWS. The installation fails because there was no TypeInstance with credentials passed to the Implementation.
Expected behavior
Render should choose Helm based Implementation.
Actual behavior
Render notices that TypeInstance with AWS credentials is available and decides to use RDS Implementation.
Steps to reproduce
Create TypeInstance with AWS credentials
Create Action for installing a database: cap.interface.database.postgresql.install
Wait for it to be Ready to run and run it.
It should fail.
Proposed solution
Instead of using all available TypeInstances consider only TypeInstance passed via Policy or directly by user.
Currently TypeInstances are get here
Description
There is a TypeInstance with AWS credentials available in the system. It's not used in any Policy and is not passed when creating an Action.
When creating a new Action, for example
cap.interface.database.postgresql.install
, renderer chooses an Implementation for AWS. The installation fails because there was no TypeInstance with credentials passed to the Implementation.Expected behavior
Render should choose Helm based Implementation.
Actual behavior
Render notices that TypeInstance with AWS credentials is available and decides to use RDS Implementation.
Steps to reproduce
cap.interface.database.postgresql.install
Proposed solution
Instead of using all available TypeInstances consider only TypeInstance passed via Policy or directly by user.
Currently TypeInstances are get here
capact/pkg/hub/client/policy_enforced_client.go
Line 55 in 21d6301
The text was updated successfully, but these errors were encountered: