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
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Add a few lines to your `package.json`. Your [account id](https://console.aws.am
52
52
53
53
### Environments
54
54
55
-
Environments for a shep project are defined by the aliases on the functions associated with a project. Environments are created through `shep deploy --env new_env` and managed by using the `shep config` commands. Shep takes a strong stance against having different environments for different functions. If shep detects that some of your functions have different aliases, it will immediately error until you remedy the issue. Most issues can be automatically fixed by using `shep config sync`, the only issues this can't solve are conflicting environment variable values. Conflicting value issues can be solved by using `shep config set my_env CONFLICT_VARIABLE=value`.
55
+
Environments for a shep project are defined by the aliases on the functions associated with a project. Environments are created through `shep deploy --env new_env` and managed by using the `shep config` commands. Shep takes a strong stance against having different environments for different functions within a project. If you attempt a command which requires the listing of environments and there is a mismatch detected, then shep will throw a `EnvironmentMistmach` error until you remedy the issue. Most issues can be automatically fixed by using `shep config sync`, the only issues this can't solve are conflicting environment variable values. Conflicting value issues can be solved by using `shep config set my_env CONFLICT_VARIABLE=value`.
Copy file name to clipboardExpand all lines: migration.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -82,4 +82,4 @@ json, and it should live inside the `/environments` directory
82
82
83
83
## Migrating from shep 3.X to shep 4.0
84
84
85
-
- Shep 4.0 now handles environment variables in AWS. See the docs for `shep config` to add, remove, list, and sync environment variables for your functions.
85
+
- Shep 4.0 now handles environment variables in the configuration of AWS Lambda Functions. If you have no undeployed changes in your `/environments` directory, then you should be able to safely delete the directory and use your exisiting project with shep `4.0.0`. See the docs for `shep config` to add, remove, list, and sync environment variables for your functions.
0 commit comments