You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for delivery to have its config stored for the project, you either have to run delivery setup with a bunch of flags that stay the same for the project between users while gitignoring the resulting cli.toml (to prevent the file from being committed with the username) or commit the cli.toml without a username and then encourage people to use the --user flag, although this doesn't work either.
You get this in the latter case:
$ delivery review
Chef Delivery
A configuration value is missing
User not set; try --user or set it in your .toml config file
$ delivery review --user myuser
error: Found argument '--user' which wasn't expected, or isn't valid in this context
USAGE:
delivery review [FLAGS] [OPTIONS]
For more information try --help
If there were some erb allowed in the cli.toml (ala Kitchen's allowance for it in kitchen.yml), you could just specify an environment variable for it or some other logic. At worst, a statically pulling the username (OPSCODE_USER?) from a specific environment variable would still be okay.
What's the best practice here? I want my developers to just be able to clone a repo and use delivery-cli without having to configure anything.
The text was updated successfully, but these errors were encountered:
@mattlqx currently you have the ability to use --user in the review command. Although that doesn't solve the big picture of this problem. I am going to work on this and I have marked this issue as an enhancement since it is not an issue anymore.
Respecting a central file for defaults (say .chef/delivery-cli.toml or similar) would be very useful for those of us with lots of projects in workflow. Having to delivery setup every project is a pain point.
@dreamnite , delivery CLI searches for its config in the same way knife and chef-client do.
Just move the cli.toml to ~/.delivery/ making sure the user, server, ent and org are all set and you'll be able to use delivery clone <project> and all the other delivery commands with no --server, --user etc switches.
Remember to remove the project specific stuff from cli.toml
In order for
delivery
to have its config stored for the project, you either have to rundelivery setup
with a bunch of flags that stay the same for the project between users while gitignoring the resulting cli.toml (to prevent the file from being committed with the username) or commit the cli.toml without a username and then encourage people to use the --user flag, although this doesn't work either.You get this in the latter case:
If there were some erb allowed in the cli.toml (ala Kitchen's allowance for it in kitchen.yml), you could just specify an environment variable for it or some other logic. At worst, a statically pulling the username (OPSCODE_USER?) from a specific environment variable would still be okay.
What's the best practice here? I want my developers to just be able to clone a repo and use delivery-cli without having to configure anything.
The text was updated successfully, but these errors were encountered: