Jaiveer Katariya
c06604910c
* Reworked AKS deployment workflows (#1403) * rebased to partner_templates * Renaming workflow * Updated corresponding properties.json files for the new aks workflows under deployments. * Updated properties.json titles for aks workflows * Renamed SECRET_NAME to IMAGE_PULL_SECRET_NAME * Moved permissions down to the job level * Updated documentation links * Updated permission for action to read * Removing redundant permissions * write -> read for actions * Updated descriptions * Less reference documentation in header * Added comments to each AKS Starter Workflow step Co-authored-by: Tommy Barnes <thbarnes@microsoft.com> * Update AKS workflows to not use imagePullSecrets (#1494) * removing old method of adding imagePullSecrets * fixing step casing * For testing: Dependency review starter workflow * changed back to image pull secret, added mask, clarified website and pull secret instructions * made changes to other aks files * Added back imagepullsecrets param to deploy action, reordered env vars * changing release version of deploy action * restructured starter workflows to parallelize secret creation and image building * renamed to buildImage and removed extra space * cleaned up some random newlines * removed extra space * removing changes from partner branch * removing changes from partner branch * through mistake in changing PR, two files lost step for createSecret Co-authored-by: Tommy Barnes <thomas.jonathan.barnes@gmail.com> Co-authored-by: Tommy Barnes <thbarnes@microsoft.com> Co-authored-by: Israel Miller <ismille@microsoft.com> Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com> Co-authored-by: Jaiveer Katariya <jaiveerkatariya@Jaiveers-MacBook-Pro.local> Co-authored-by: Jaiveer Katariya <jaiveerkatariya@rgoldshtein.middleeast.corp.microsoft.com>
Starter Workflows
These are the workflow files for helping people get started with GitHub Actions. They're presented whenever you start to create a new GitHub Actions workflow.
If you want to get started with GitHub Actions, you can use these starter workflows by clicking the "Actions" tab in the repository where you want to create a workflow.
Directory structure
- ci: solutions for Continuous Integration workflows.
- deployments: solutions for Deployment workflows.
- automation: solutions for automating workflows.
- code-scanning: starter workflows for Code Scanning
- icons: svg icons for the relevant template
Each workflow must be written in YAML and have a .yml extension. They also need a corresponding .properties.json file that contains extra metadata about the workflow (this is displayed in the GitHub.com UI).
For example: ci/django.yml and ci/properties/django.properties.json.
Valid properties
name: the name shown in onboarding. This property is unique within the repository.description: the description shown in onboardingiconName: the icon name in the relevant folder, for example,djangoshould have an iconicons/django.svg. Only SVG is supported at this time. Another option is to use octicon. The format to use an octicon isocticon <<icon name>>. Example:octicon personcreator: creator of the template shown in onboarding. All the workflow templates from an author will have the samecreatorfield.categories: the categories that it will be shown under. Choose at least one category from the list here. Further, choose the categories from the list of languages available here. When a user views the available templates, those templates that match the same language will feature more prominently.
Categories
- continuous-integration
- deployment
- testing
- code-quality
- code-review
- dependency-management
- monitoring
- Automation
- utilities
Variables
These variables can be placed in the starter workflow and will be substituted as detailed below:
$default-branch: will substitute the branch from the repository, for examplemainandmaster$protected-branches: will substitute any protected branches from the repository$cron-daily: will substitute a valid but random time within the day