Commit b1d339d5 authored by Adam Hawkins's avatar Adam Hawkins

Fix Saltside references

parent bfe0fa8f
Pipeline #3632769 passed with stages
in 26 seconds
......@@ -75,7 +75,7 @@ required to get going. It contains a few important bits:
1. `vagrant-workstation` committed as a submodule so there is never a
conflict of what `vagrant-workstation` is required for this
project.
1. The `saltside-workstation` command for all team specific
1. The `slashdeploy-workstation` command for all team specific
functionality.
1. `script/host-check` and `script/configure-guest`. I'll talk more
about this later.
......@@ -85,7 +85,7 @@ The `slashdeploy-workstation` command wraps the necessary calls. Using
a wrapper command provides a few key benefits:
* Sets `WORKSTATION_NAME` environment variable so
`saltside-workstation` may be invoked from anywhere on the host
`slashdeploy-workstation` may be invoked from anywhere on the host
system. `vagrant-workstation` supports multiple VMs, so this
commands always targets this specific one.
* Allows layering of team specific requirements on top of
......@@ -108,12 +108,12 @@ uses the values to do specific configuration.
Here's how an example for AWS per-user AWS keys work. The user exports
`SLASHDEPLOY_AWS_ACCESS_KEY_ID` and
`SLASHDEPLOY_AWS_SECRET_ACCESS_KEY` on their host system. The
`saltside-workstation provison` runs which runs
`slashdeploy-workstation provison` runs which runs
`script/configure-guest`.
Here is the `configure` function called during the `provision`
command. See the complete [source][] for the full
`saltside-workstation` file.
`slashdeploy-workstation` file.
# Capture all SLASHDEPLOY prefixed environment variables in a file
# that will be accessible in the VM. Then run script inside the VM
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment