Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ygo74/iac
Last synced: 6 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/ygo74/iac
- Owner: ygo74
- License: mit
- Created: 2020-02-03T21:30:03.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2020-04-27T09:20:41.000Z (over 4 years ago)
- Last Synced: 2024-11-09T04:36:50.368Z (2 months ago)
- Size: 445 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Infrastructure As Code
## Project status
| Item | status |
|--------------|--------------------------------------------------------------------------------------------------------------------|
| License | [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/ygo74/iac_tools/blob/master/LICENSE) |
| Build status | [![Build Status](https://dev.azure.com/ygo74/iac/_apis/build/status/ygo74.iac?branchName=master)](https://dev.azure.com/ygo74/iac/_build/latest?definitionId=21&branchName=master) |## Project structure
## Application Definitions
Application definition is defined at different levels :
=> Global Application
=> Environment## Tools
## Manage Infrastructure version
file: infrastructure/version.yml
format:
```yaml
---
# Format must be :
# version: Major.Minor
version: 1.0
```### Strategy
1. Update Major Version
When: Global configuration changes which impact all applications
How: Manual, Modify the file infrastructure/version.yml2. Update Minor Version
When: New application is added
How: Manual, Modify the file infrastructure/version.yml3. Update Patch Version
When: Pull request is merged on master
How: Bump patch version on the latest tag found for pattern Major.Minor### Questions
1. Do we want to address fix on older version ?
If yes, we have to see how we merge fix for old version in master ? need to read version from version.yml file to compare master against last tags.