added new action to build + push to azure #2152
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| name: Build + Push to Azure | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
| inputs: | ||
| branch: | ||
| description: "Source branch to deploy" | ||
| required: false | ||
| default: "main" | ||
|
There was a problem hiding this comment. I think source branch should be required, and not default to main. This way someone doesn't accidentally publish our docs from the main branch, since we want our published docs to always be from a release branch. |
||
| type: string | ||
| environment: | ||
| description: "Determines where build gets pushed to" | ||
| required: false | ||
| default: "preview" | ||
| type: choice | ||
| options: | ||
| - preview | ||
| - dev | ||
| - staging | ||
| - prod | ||
| push: | ||
| branches: | ||
| - main | ||
|
There was a problem hiding this comment. Similar to the comment above, I'm assuming this is going to publish our public docs for every push to main? if so, we don't want that behavior, we only publish from our latest release branch. |
||
| paths: | ||
| - nginx-gateway-fabric/site/content | ||
| pull_request: | ||
| branches: | ||
| - "*" | ||
| jobs: | ||
| call-docs-build-push: | ||
| uses: nginxinc/docs-actions/.github/workflows/docs-build-push.yml@main | ||
| with: | ||
| production_url_path: "/nginx-gateway-fabric" | ||
| preview_url_path: "/previews/nginx-gateway-fabric/" | ||
| docs_source_path: "./site/content/" | ||
| docs_build_path: "./site/" | ||
| doc_type: "hugo" | ||
| secrets: | ||
| AZURE_CREDENTIALS: ${{secrets.AZURE_CREDENTIALS}} | ||
| AZURE_KEY_VAULT: ${{secrets.AZURE_KEY_VAULT}} | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add "docs" to this name (and the name of the file itself) so it's clear what this is for? (and not the product).