v1.0.0

Use GitOps Configuration File @goruha (#15)

what

• Use a configuration file instead of passing all parameters as inputs

why

• Makes it easier in reusable workflows to reuse actions without needing to edit workflows themselves
• Separate business logic from configuration

Migrating from v0 to v1

v1 replace jq-query input with selected-filter variable and simplify the query.
Now you need to specify only part used in select function of jq-query.

v1 moved variables from inputs to atmos gitops config path ./.github/config/atmos-gitops.yaml

name
atmos-version
atmos-config-path

If you want the same behavior in v1 as inv0 you should create config ./.github/config/atmos-gitops.yaml with the same variables as in v1 inputs.

  - name: Selected Components
    id: components
    uses: cloudposse/github-action-atmos-terraform-select-components@v1
    with:
      atmos-gitops-config-path: ./.github/config/atmos-gitops.yaml
      select-filter: '.settings.github.actions_enabled // false'

same behaviour as

  - name: Selected Components
    id: components
    uses: cloudposse/github-action-atmos-terraform-select-components@v0
    with:
      atmos-config-path: "${{ github.workspace }}/rootfs/usr/local/etc/atmos/"
      jq-query: 'to_entries[] | .key as $parent | .value.components.terraform | to_entries[] | select(.value.settings.github.actions_enabled // false) | [$parent, .key] | join(",")'

v0.2.0

Added major release tagger @zdmytriv (#10)

what

• Added major release tagger

why

• Added major release tagger

references

v0.1.0

Initial @zdmytriv (#4)

what

• Initial implementation

why

• Initial implementation

references