[BOLT-503] Use local config automatically to embed bolt in a project Created: 2018/04/27  Updated: 2018/06/20  Resolved: 2018/06/20

Status: Resolved
Project: Puppet Task Runner
Component/s: None
Affects Version/s: None
Fix Version/s: BOLT 0.21.0

Type: Story Priority: Normal
Reporter: Alex Dreyer Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: docs, docs-reviewed, feature
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to BOLT-523 I want to install modules with bolt Resolved
Template:
Team: Bolt
Sprint: Bolt Kanban
Release Notes: New Feature
QA Risk Assessment: Needs Assessment

 Description   

I want to use bolt as a tool to manage my applications including everything needed with the application repo itself.

Currently this is possible by including bolt.yaml at the top level of your project, in bolt.yaml point to a modules an inventory inside the project repo. But then every command needs to be run with --config=$PROJECT_PATH/bolt.yaml.

Solutions:

When bolt runs it should search the cwd and its ancestors for a directory called Boltdir. If one is found the bolt should run in Boltdir mode where default location for bolt.yaml, inventory.yaml should be at the top level of the Boltdir and the modulepath should default to [ Boltdir/modules/ ]

Users should be able to specify the boltdir from the commandline with --boltdir.

The global config and inventory should not be loaded by default when running in Boltdir mode.



 Comments   
Comment by Alex Dreyer [ 2018/05/17 ]

I broke the module installation features into their own ticket BOLT-523. I think a command to initialize an empty boltdir should be a separate ticket as well.

Generated at Wed Nov 13 11:48:23 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.