Bump ansible/ansible-content-actions/.github/workflows/build_import.yaml from 8d811a21e588dc6692299797e9a2bab1205365dc to 46de405af31ba872a770a9b75c90121493c1cbe5

[dependabot]

Bumps ansible/ansible-content-actions/.github/workflows/build_import.yaml from 8d811a21e588dc6692299797e9a2bab1205365dc to 46de405af31ba872a770a9b75c90121493c1cbe5.

Changelog

Sourced from ansible/ansible-content-actions/.github/workflows/build_import.yaml's changelog.

Using the release workflow

This GitHub action releases the collection in Ansible Automation Hub and Ansible Galaxy, it is dependent on the environment release which must contain the following secrets.

AH_TOKEN: The Automation Hub token required for to interact with Ansible Automation Hub. ANSIBLE_GALAXY_API_KEY: A Galaxy token required to interact with Ansible Galaxy.

Note - ansible-content-actions/release.yaml uses release_ah.yaml and release_galaxy.yaml internally.

Filename: release.yaml

---
name: "Release collection"
on:
  release:
    types: [published]
jobs:
release:
uses: ansible/ansible-content-actions/.github/workflows/release.yaml@main
with:
environment: release
secrets:
ah_token: ${{ secrets.AH_TOKEN }}
ansible_galaxy_api_key: ${{ secrets.ANSIBLE_GALAXY_API_KEY }}

The workflow run results in -

The release works in two parts, Automation hub release and then Ansible Galaxy release. If the Automation hub release fails, the Galaxy job is skipped.

Example showing how only Automation hub release can be made, only ah_token would be required in those cases.

Release on AH only, workflow

Filename: release_ah.yaml

---
name: "Release collection on AH"
on:
  release:
    types: [published]
jobs:
release_automation_hub:
uses: ansible/ansible-content-actions/.github/workflows/release_ah.yaml@main
</tr></table>

... (truncated)

Commits

• 46de405 chore(deps): update release-drafter/release-drafter action (#100)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)