inspec/test/fixtures/profiles/dependencies/profile_b/inspec.yml

name: profile_b
title: InSpec Profile
maintainer: The Authors
copyright: The Authors
copyright_email: you@example.com
license: Apache-2.0
summary: An InSpec Compliance Profile
version: 0.1.0
depends:
  - name: profile_d
    path: ../profile_d
Fix recursive deps for path-based deps Signed-off-by: Steven Danna <steve@chef.io> 2016-08-17 13:25:07 +00:00			`name: profile_b`
			`title: InSpec Profile`
			`maintainer: The Authors`
			`copyright: The Authors`
			`copyright_email: you@example.com`
Remove any "All Rights Reserved" references (#1969) * Remove any "All Rights Reserved" references InSpec is licensed and released under the Apache 2.0 license. This change removes all reference to legacy code files that still had any Copyright or License lines referring to "All Rights Reserved". Signed-off-by: Adam Leff <adam@leff.co> * fix functional tests Signed-off-by: Christoph Hartmann <chris@lollyrock.com> 2017-06-28 11:14:19 +00:00			`license: Apache-2.0`
Fix recursive deps for path-based deps Signed-off-by: Steven Danna <steve@chef.io> 2016-08-17 13:25:07 +00:00			`summary: An InSpec Compliance Profile`
			`version: 0.1.0`
Initial control isolation support The goal of this change is to provide an isolated view of the available profiles when the user calls the include_controls or require_controls APIs. Namely, - A profile should only be able to reference profiles that are part of its transitive dependency tree. That is, if the dependency tree for a profile looks like the following: A \|- B --> C \| \|- D --> E Then profile B should only be able to see profile C and fail if it tries to reference A, D, or E. - The same profile should be include-able at different versions from different parts of the tree without conflict. That is, if the dependency tree for a profile looks like the following: A \|- B --> C@1.0 \| \|- D --> C@2.0 Then profile B should see the 1.0 version of C and profile D should see the 2.0 profile C with respect to the included controls. To achieve these goals we: - Ensure that we construct ProfileContext objects with respect to the correct dependencies in Inspec::DSL. - Provide a method of accessing all transitively defined rules on a ProfileContext without pushing all of the rules onto the same global namespace. This does not yet handle attributes or libraries. 2016-08-24 11:17:29 +00:00			`depends:`
			`- name: profile_d`
			`path: ../profile_d`