Skip to content

AzActions/actions

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AzActions - Trying to make things easier

We have decided to create custom actions that provide a simpler approach by default, while keeping the flexibility of advanced scenarios through use of inputs. For details on why we chose to create a custom action, please review the action documentation. Each of them have a "Why use this module?" segment in their readme.

Action name (link to doc) Description Status Latest version Last update Size Issues
AzActions/Variables Manage workflow variables Action-Test GitHub tag (latest SemVer) GitHub tag (latest SemVer pre-release) GitHub last commit (branch) GitHub repo size GitHub issues GitHub pull requests
AzActions/AzConnect Connect to Azure Action-Test GitHub tag (latest SemVer) GitHub tag (latest SemVer pre-release) GitHub last commit (branch) GitHub repo size GitHub issues GitHub pull requests
AzActions/AzGather Gather Azure environment info Action-Test GitHub tag (latest SemVer) GitHub tag (latest SemVer pre-release) GitHub last commit (branch) GitHub repo size GitHub issues GitHub pull requests
AzActions/AzModules Deploy resources to Azure Action-Test GitHub tag (latest SemVer) GitHub tag (latest SemVer pre-release) GitHub last commit (branch) GitHub repo size GitHub issues GitHub pull requests
AzActions/AzUtilities Installs utilities on runner Action-Test GitHub tag (latest SemVer) GitHub tag (latest SemVer pre-release) GitHub last commit (branch) GitHub repo size GitHub issues GitHub pull requests

Input handling

Most of our actions will start with loading environment variables, named the same as the different action inputs. This can be seen as setting the default values for the actions within a workflow, reducing the need of repeating them throughout the workflow. After environment variables are loaded, the inputs are gathered and merged with the inputs overriding the defaults from environment variables. If default values are provided in the inputs section of the action definition, this will also override the gathered environment variables.

Note!

This override mechanism will only be used for a specific call of the action, and will not store the overridden value back to the corresponding environment variable.

Used together with AzActions/Variables and a variables file which can be stored as code and loaded,we try to reduce the duplication specifying inputs.

Repo automation

To automate setup of our action we use:

App name Configuration Description
Release Drafter .github/release-drafter.yml Drafts your next release notes as pull requests are merged.
Work In Progress Use 'WIP or 'wip' in PR title. Prevent merging of Pull Requests with "WIP" in the title
Request Info .github/config.yml Automatically requests more info on issues and pull requests with the default title or an empty body.
Settings .github/settings.yml Repo configuration as code.

How to contribute

Coming soon.

Code of Conduct

Coming soon.

Code quality and guidelines

Coming soon.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published