| Service | Event Names | Description |
|---|---|---|
| accessanalyzer | ApplyArchiveRule | |
| CancelPolicyGeneration | Cancels the requested policy generation. |
|
| CreateAccessPreview | Creates an access preview that allows you to preview IAM Access Analyzer findings for your resource before deploying resource permissions. |
|
| CreateAnalyzer | Creates an analyzer for your account. |
|
| CreateArchiveRule | ||
| DeleteAnalyzer | ||
| DeleteArchiveRule |
Leading a software development team and sick of telling everyone to
yarn installinstead ofnpm installeverytime? Annoyed by someone checking inpackage-lock.json? All these issue could have been avoided by usingone-package-manager.
One-package-manager is an un-opinionated script for Javascript Projects to help enforcing the use of Yarn or NPM consistently within a software development team that requires no installation and minimal configuration.
To enable one-package-manager, simply adding the following to your package.json:
{Starting a personal node project could be easy; starting a team node project could be challenging.
I am a developer currently working in SEEK Australia.
In my experience, common mistakes developer make when starting a projects are:
- No Linting
| parse_git_branch() { | |
| git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/' | |
| } | |
| export PS1="\u@\h \[\033[32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] $ " |
