inspec/test/fixtures/profiles/dependencies/profile_d/controls/example.rb

# you add controls here
control 'profiled-1' do                        # A unique ID for this control
  impact 0.7                                # The criticality, if this control fails.
  title 'Create / directory (profile d)'             # A human-readable title
  desc 'An optional description...'
  describe file('/') do                  # The actual test
    it { should be_directory }
  end
end
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			`# you add controls here`
			`control 'profiled-1' do # A unique ID for this control`
			`impact 0.7 # The criticality, if this control fails.`
Changed a bunch of profiles to use / instead of /tmp for Windows compat. 2019-11-06 22:40:00 +00:00			`title 'Create / directory (profile d)' # A human-readable title`
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			`desc 'An optional description...'`
Changed a bunch of profiles to use / instead of /tmp for Windows compat. 2019-11-06 22:40:00 +00:00			`describe file('/') do # The actual test`
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			`it { should be_directory }`
			`end`
			`end`