Skip to content

Config file requires absolute path #29

@eldeal

Description

@eldeal

dp-setup-path: "path/to/your/dp-setup/project"

If this path is a relative path (~/Development/git/ons/dp-setup for example) then an error is thrown when trying to run the tool saying:

[dp-cli] error creating group commands for env: production: error loading ansible hosts for production : open ~/Development/git/ons/dp-setup/ansible/inventories/production/hosts: no such file or directory

It wasn't immediately obvious to me that this was a path issue, because if you take the path and do an ls it does work. I was suspicious of file permissions and going down rabbit holes.

Perhaps updating the documentation to something like /absolute/path/to/your/dp-setup/project would provide better clarity?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions