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
Below is the reason this RPC is different than all the other RPC in the cfgmgmt.proto.
This RPC returns node data and only passes a revisionId. The data returned is searched for in the chef actions. Because this is node data we cannot use the project filtering when pulling the information out of the Chef action indexes. Extra information; the revisionId is also a field on the node-state and converge-history indexes.
One solution is to use the revisionId to request the latest Run with a matching field. Then request that run's associated node to retrieve its projects.
Another solution is to move the policy cookbook information out of the action and store it with the correct associated node.
The preference would be the former solution, but it depends on how much effort it will take.
@kmacgugan would be a good reference for this work.
Definition of Done
The GetPolicyCookbooks API will filter on projects.
Demo Script / Repro Steps
Create a policy cookbook
Run a CCR
Add projects to the CCR node
Ensure that a user with access to that project can request the information.
Ensure that a user without access to that project cannot request the information.
The text was updated successfully, but these errors were encountered:
lancewf
added
the
iamv2
This issue or pull request applies to iamv2 work for Automate
label
May 17, 2019
User Story
In order to ensure a user has access to the information in the GetPolicyCookbooks RPC project filtering must be added.
This issue is an extension of the #68 issue.
Below is the reason this RPC is different than all the other RPC in the
cfgmgmt.proto
.This RPC returns node data and only passes a
revisionId
. The data returned is searched for in the chef actions. Because this is node data we cannot use the project filtering when pulling the information out of the Chef action indexes. Extra information; therevisionId
is also a field on the node-state and converge-history indexes.One solution is to use the
revisionId
to request the latest Run with a matching field. Then request that run's associated node to retrieve its projects.Another solution is to move the policy cookbook information out of the action and store it with the correct associated node.
The preference would be the former solution, but it depends on how much effort it will take.
@kmacgugan would be a good reference for this work.
Definition of Done
The
GetPolicyCookbooks
API will filter on projects.Demo Script / Repro Steps
The text was updated successfully, but these errors were encountered: