Skip to content

Commit

Permalink
Update README
Browse files Browse the repository at this point in the history
  • Loading branch information
goruha committed Dec 9, 2023
1 parent e77c819 commit 52b67ea
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,8 +106,8 @@ components:
## Migrate `v1` to `v2`

Starting from `v2` the action do not restrict component config just to `settings` section.
If you want `v2` having the same behaviour as `v1` you should add `settings` in `settings-path` variable.
Starting from `v2` the action is no longer restricted to retrieving the component config from only the `settings` section..
If you want the same behavior in `v2` as in`v1`, you should add the `settings` prefix to the value of the `settings-path` variable.

```yaml
- name: Get Atmos Setting for Secret ARN
Expand Down
6 changes: 3 additions & 3 deletions README.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,10 @@ usage: |-
secret-ids: ${{ steps.example.outputs.value }}
```
## Migrate `v1` to `v2`
## Migrating from `v1` to `v2`
Starting from `v2` the action do not restrict component config just to `settings` section.
If you want `v2` having the same behaviour as `v1` you should add `settings` in `settings-path` variable.
Starting from `v2` the action is no longer restricted to retrieving the component config from only the `settings` section..
If you want the same behavior in `v2` as in`v1`, you should add the `settings` prefix to the value of the `settings-path` variable.
```yaml
- name: Get Atmos Setting for Secret ARN
Expand Down

0 comments on commit 52b67ea

Please sign in to comment.