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
As discussed in the iamv2 meeting yesterday (4/11), for the initial implementation of projects filtering for compliance-service we are ignoring the case where incoming requests have no project data attached. By design all requests should include projects data, so this is guarding at the seams between services that this assumption is being maintained.
Being lenient to non-compliant requests is useful in the short term to allow existing code that has no knowledge of projects to continue working, but eventually we will want to be strict in how that is handled.
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
Related to chef/a2#5116
As discussed in the iamv2 meeting yesterday (4/11), for the initial implementation of projects filtering for
compliance-service
we are ignoring the case where incoming requests have no project data attached. By design all requests should include projects data, so this is guarding at the seams between services that this assumption is being maintained.Being lenient to non-compliant requests is useful in the short term to allow existing code that has no knowledge of projects to continue working, but eventually we will want to be strict in how that is handled.
The text was updated successfully, but these errors were encountered: