mirror of
https://github.com/inspec/inspec
synced 2024-09-20 14:31:58 +00:00
2bbcdbde9b
* Remove deprecated yumrepo. (#3435) * Remove deprecations for cli `--format` and metadata.rb (#3452) * Remove deprecated database_helpers stderr/stdout methods. Update deprecation text for processes/apache. * Remove deprecations for `--format` and metadata.rb Remove deprecated `format` code. Remove deprecated code test and change json-config format test to use reporter. Remove deprecated metadata.rb code Remove deprecation notice for old supports syntax. Deprecate metadata.rb from source_reader Remove rubocop disables as they are no longer required for this code block. Remove deprecated legacy metadata.rb mock profiles. Remove deprecated metadata.rb profile tests. Remove deprecated yumrepo test. * Allow inspec-3.0 branch to be tested. * Allow appveyor to test inspec-3.0 branch * Change runner tests to use reporter rather than format. Remove deprecated `supports: linux` tests. * Remove skip from inherited profiles from showing up in reporting (breaking change) (#3332) * Skip loading dependency profiles if they are unsupported on the current platform. Skip loading dependencies if they are unsupported on the current platform. Wrap our log and next in a conditional checking if the platform is supported. Change a `if !` into a `unless` Check if the backend is a Train Mock Connection and if so say that the profile does support the platform. While iterating through tests being loaded skip when the platform is unsupported. We now log a WARN when a profile is skipped due to unsupported platform, so lets check that. Modified existing test to log that there are 0 skipped tests, instead of 2. Add functional test that loads profile-support-skip with a json reporter to check that our controls are not loaded and that stderr contains our warning. * Rather than iterating through each test return before recursion if the platform is unsupported. * Resolve tests using a supported platform different from testing platform Add a control to `test/unit/mock/profiles/complete-profile` that would work on any OS with a Internet connection. This allows the profile to execute on any OS with success. `filesystem_spec.rb` was a control that would only work on Linux and some BSD's. We want profile tests to consistently work across development and testing platforms, and not get 'skipped' in some cases. Travis-CI tests on Linux, Inspec Dev team uses Linux and MacOS, Appveyor tests on Windows Also Updated `file_provider_test.rb` for `complete-profile` content changes. If you `MockLoader.load_profile` on a unsupported platform you might not hit the usual skip. Lets handle situations where the tests array in Profile#load_checks_params could be nil. * Use safe navigation rather than checking if tests is nil. Update tests to point to unsupported_inspec and account for WARN changes. Make unsupported_inspec profile support os-family 'unsupported_inspec' * Fix skip bug when using include/require controls. (#3487) * Fix skip bug when using include/require controls. * fix test and feedback. * Remove need for UUID detection for Automate report (#3507) * Add json metadata for skipped profiles (#3495) * Add skip metadata to json reports * Unify skip messages. * Update with status field. * Add testing. * Fix tests. * lint * Add skip exit codes for profile skips. * Update website for 3.0 launch Add `plugins` to sidebar. Change 2.0 -> 3.0 in slim files. Update 3.0 features list. * Fix comments * Update float to numeric. * Change Float to numeric. * updated feature list and impact doc * Change "What's new in InSpec 3.0" -> "Announcing InSpec 3.0" * Bump VERSION to 3.0.0 (#3511) * Remove 3.0 testing checks. * Fix azure link. |
||
|---|---|---|
| .. | ||
| data | ||
| lib | ||
| source | ||
| .gitignore | ||
| config.rb | ||
| config.ru | ||
| Gemfile | ||
| Rakefile | ||
| README.md | ||
InSpec homepage
Development
Get all dependencies:
bundle install
To build the docs/ child pages run:
bundle exec rake docs
To run it live run:
bundle exec middleman server
For the online demo, take a look at www/demo.
Building
To build the site to a local static folder (without demo):
bundle exec middleman build
- if you get an error building the css files it could be becuase you don't have node.js installed. e.g.
== Request: /stylesheets/vendor/fontawesome.min.css
== Finishing Request: stylesheets/vendor/fontawesome.min.css (0.0s)
error build/stylesheets/vendor/fontawesome.min.css
To build everything including the online demo:
bundle exec rake www:build
Releasing
To build everything and push a new version of the website, be in the www folder of this repository and run:
bundle install
bundle exec rake www
It will clear everything and build from scratch and create a local gh-pages branch with a static version of the website.
Before pushing, it will ask you if you are happy with it.
Please verify the site now! To host the current folder you can run:
ruby -run -e httpd . -p 8000
Open your browser to localhost:8000.
If you are happy, you can confirm the site and let the release task push it live.
Flushing the Fastly Cache
The www Rake task will flush the cache at Fastly if you have the following environment variables set:
FASTLY_API_KEYFASTLY_SERVICE_ID
These can be found in Chef's shared password manager. If these aren't set, the cache will not be flushed and will expire on its own. The cache can be flushed without doing a full website release by running rake www:flush