Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates azure.yaml schema to support single or multi hook configuration #4265

Merged
merged 1 commit into from
Sep 5, 2024

Conversation

wbreza
Copy link
Contributor

@wbreza wbreza commented Aug 28, 2024

Updates azure.yaml schema to support both single and multi-hook configuration

Important

Should not merge till release day since schema updates are not managed as part of the release.

Supports single hook per event (legacy)

name: test-proj
services:
    api:
        project: src/api
        host: containerapp
        language: ts
        hooks:
            postprovision:
                shell: sh
                run: scripts/postprovision.sh
hooks:
    postprovision:
        shell: sh
        run: scripts/postprovision.sh

Supports multiple hooks per event (new)

name: test-proj
services:
    api:
        project: src/api
        host: containerapp
        language: ts
        hooks:
            postprovision:
                - shell: sh
                  run: scripts/postprovision1.sh
                - shell: sh
                  run: scripts/postprovision2.sh
hooks:
    postprovision:
        - shell: sh
          run: scripts/postprovision1.sh
        - shell: sh
          run: scripts/postprovision2.sh

@wbreza wbreza changed the title Updates schema to support single or multi hook configuration Updates azure.yaml schema to support single or multi hook configuration Aug 28, 2024
@wbreza
Copy link
Contributor Author

wbreza commented Aug 28, 2024

/check-enforcer override

@wbreza wbreza merged commit 4285526 into Azure:main Sep 5, 2024
4 checks passed
@wbreza wbreza deleted the multi-hook-schema-updates branch September 5, 2024 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants