Closed sbaidachni closed 6 months ago
In this PR we are adding GitHub stages for Azure Function deployment. PR is deploying into the branch slot, and CI is deploying into the default slot into the development environment.
PR Build should be successfully executed for this PR, and functions should be deployed.
Additional fixes has been applied to build_indexer module. Now, it's creating an index and data source based on the branch name. Skillset and Indexer creation has not been tuned in this PR.
What do you mean by PR is deploying into the branch slot, and CI is deploying into the default slot into the development environment.
Also let us work together to create a workable README or a quick start
@mhassaninmsft Ari is working at initial readme. Regarding to the description, PR Build is deploying Azure Functions into a slot that has been created for the branch (automatically), and CI Build is deploying Azure Functions into the production (default) slot right after merge to make sure that we have a stable version of the functions to test other services if needed.
In this PR we are adding GitHub stages for Azure Function deployment. PR is deploying into the branch slot, and CI is deploying into the default slot into the development environment.
PR Build should be successfully executed for this PR, and functions should be deployed.
Additional fixes has been applied to build_indexer module. Now, it's creating an index and data source based on the branch name. Skillset and Indexer creation has not been tuned in this PR.