Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve lockfile handling #1070

Closed
chris-rock opened this issue Sep 14, 2016 · 0 comments
Closed

Improve lockfile handling #1070

chris-rock opened this issue Sep 14, 2016 · 0 comments
Labels
Type: Enhancement Improves an existing feature
Milestone

Comments

@chris-rock
Copy link
Contributor

chris-rock commented Sep 14, 2016

Description

At this time, the lockfile is only generated when we use inspec vendor. We need to improve and simplify the handling for users:

Is the lock file is generated all the time?

  • we always create a lock-file
  • make it visible in our CLI output with profile location, eg “loaded from cache [cachedir]"
  • create a lock file separately for each target

Are lockfiles generated for remote profile

  • we do not create a lock file for remote profiles

lockfile + cache available

  • use information from lockfile
  • no remote connectivity required if we have everything in cache

lockfile + profile not available in cache and not downloadable

  • display error, no further execution possible

Related to #888

@chris-rock chris-rock added the Type: Enhancement Improves an existing feature label Sep 14, 2016
@chris-rock chris-rock added this to the 0.35.0 milestone Sep 14, 2016
@arlimus arlimus added the ready label Sep 15, 2016
@chris-rock chris-rock modified the milestones: 0.35.0, 0.36.0 Sep 19, 2016
@chris-rock chris-rock modified the milestones: 0.36.0, 1.0.0 Sep 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Improves an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants