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
the basic upgrade path
run chef-automate iam version: expect response of IAM v1.0
create local user
add compliance nodes (chef_load_compliance_scans -N 10). this will create nodes for client runs and compliance.
add some actions (chef_load_actions)
run the upgrade command: chef-automate iam upgrade-to-v2 --beta2.1
logged in as admin:
navigate to client runs: expect to see the nodes
navigate to compliance: expect to see the nodes
navigate to event feed: expect to see the actions
logged in as local user:
navigate to client runs: expect to see the nodes
navigate to compliance: expect to see the nodes
navigate to event feed: expect to see the actions
creating node ingestion rules tags node reports with projects (client runs AND compliance)
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the nodes.
request all nodes without projects (via api or ui)
expect to only the nodes that did not match the ingestion rules ("unassigned")
a) request all nodes in one project: ensure data matches
b) request all nodes in both projects: ensure data matches
c) request all nodes in both projects and all nodes that did not match: expect to see all nodes (a + b)
add more nodes.
repeat a, b, and c from above
creating actions ingestion rules tags actions (events) with projects note: this does not apply to events from scan jobs and profiles. this only refers to "actions"
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the actions.
request all actions without projects (via api or ui)
expect to only the actions that did not match the ingestion rules ("unassigned")
a) request all actions in one project: ensure data matches
b) request all actions in both projects: ensure data matches
c) request all actions in both projects and all that did not match: expect to see all actions (a + b)
add more actions.
repeat a, b, and c from above
data access integrity
< after upgrading to iamv2 >
while logged in as admin, request nodes from the earlier referenced projects
navigate to the node details view for one of the nodes in client runs. save the url.
navigate to the node details view for one of the nodes in compliance. save the url.
log in as a different user, that does not have access to the projects
copy and paste the urls; expect 403
The text was updated successfully, but these errors were encountered:
vjeffrey
added this to the
iamv2: ingested nodes & actions milestone
Apr 14, 2019
vjeffrey
added
iamv2
This issue or pull request applies to iamv2 work for Automate
chef-conf
This issue is being targeted for delivery by chef conf
labels
Apr 14, 2019
the basic upgrade path
run
chef-automate iam version
: expect response ofIAM v1.0
create local user
add compliance nodes (
chef_load_compliance_scans -N 10
). this will create nodes for client runs and compliance.add some actions (
chef_load_actions
)run the upgrade command:
chef-automate iam upgrade-to-v2 --beta2.1
logged in as admin:
logged in as local user:
creating node ingestion rules tags node reports with projects (client runs AND compliance)
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the nodes.
request all nodes without projects (via api or ui)
expect to only the nodes that did not match the ingestion rules ("unassigned")
a) request all nodes in one project: ensure data matches
b) request all nodes in both projects: ensure data matches
c) request all nodes in both projects and all nodes that did not match: expect to see all nodes (a + b)
add more nodes.
repeat a, b, and c from above
creating actions ingestion rules tags actions (events) with projects
note: this does not apply to events from scan jobs and profiles. this only refers to "actions"
< after upgrading to iamv2 >
create some ingestion rules in two different projects. ensure the fields selected will match a subset of the actions.
request all actions without projects (via api or ui)
expect to only the actions that did not match the ingestion rules ("unassigned")
a) request all actions in one project: ensure data matches
b) request all actions in both projects: ensure data matches
c) request all actions in both projects and all that did not match: expect to see all actions (a + b)
add more actions.
repeat a, b, and c from above
data access integrity
< after upgrading to iamv2 >
while logged in as admin, request nodes from the earlier referenced projects
navigate to the node details view for one of the nodes in client runs. save the url.
navigate to the node details view for one of the nodes in compliance. save the url.
log in as a different user, that does not have access to the projects
copy and paste the urls; expect 403
The text was updated successfully, but these errors were encountered: