Chef Automate provides a full suite of enterprise capabilities for maintaining continuous visibility into application, infrastructure, and security automation.
I want to be able to assign manually added nodes and node integrations to projects. I want to ensure those nodes and node integrations (+ all nodes added by those integrations) are only viewable by ppl with access to those projects.
This is a continuation of the rbac work that was done on ingested nodes. Since these resources are created in Automate, users will be able to manually select which projects the nodes/node integrations should belong to (instead of using ingest rules like we do for ingested nodes)
CUSTOMER IMPACT:
Users need a way to assign nodes/node integrations to projects to be able to ensure the correct ppl have access to those resources.
ACCEPTANCE CRITERIA:
project select widget present on node add and node integration add screens
project select widget present on node edit and node integration edit screens
a manually added node or node added via integration should have project information included in scan report
TEST SCENARIO:
add a couple nodes, assign to projects
add a couple node integrations, assign to projects
switch to a project view that was not selected during resource creation == don't see the resources
switch to a project view that should only have some of the resources, ensure expectations match result
run a scan on a few nodes
ensure the scanned node object, viewable from compliance reporting, reflects the same projects assignment as the manually created resource
PROBLEM STATEMENT:
I want to be able to assign manually added nodes and node integrations to projects. I want to ensure those nodes and node integrations (+ all nodes added by those integrations) are only viewable by ppl with access to those projects.
This is a continuation of the rbac work that was done on ingested nodes. Since these resources are created in Automate, users will be able to manually select which projects the nodes/node integrations should belong to (instead of using ingest rules like we do for ingested nodes)
CUSTOMER IMPACT:
Users need a way to assign nodes/node integrations to projects to be able to ensure the correct ppl have access to those resources.
ACCEPTANCE CRITERIA:
TEST SCENARIO:
Aha! Link: https://chef.aha.io/epics/A2-E-143