terraform-gitlab-environment
terraform-gitlab-environment for gitlab
Requirements
This is a list of plugins that need to be installed previously to enjoy all the goodies of this configuration:
Usage
module "main" {
source = "hadenlabs/environment/gitlab"
version = "0.0.0"
project_name = "organization/project"
variables = {
"key" = "value"
}
}
Full working examples can be found in examples folder.
Examples
common
module "main" {
source = "hadenlabs/environment/gitlab"
version = "0.0.0"
}
Requirements
| Name | Version |
|---|---|
| terraform | >= 0.13 |
| gitlab | >=3.5.0 |
Providers
| Name | Version |
|---|---|
| gitlab | >=3.5.0 |
Modules
No modules.
Resources
| Name | Type |
|---|---|
| gitlab_project_variable.this | resource |
| gitlab_project.this | data source |
Inputs
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| project_name | The name of project ex: namespace/repository | string |
n/a | yes |
| scope | The scope of variables | string |
"*" |
no |
| variables | Variables for group. | map(any) |
{} |
no |
Outputs
| Name | Description |
|---|---|
| instance | output instance gitlab_variable |
| project | output instance gitlab_project |
| project_name | output project name |
| scope | output scope |
| variables | List of variables available. |
Help
Got a question?
File a GitHub issue.
Contributing
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or file feature requests.
Development
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
-
Fork the repo on GitHub
-
Clone the project to your own machine
-
Commit changes to your own branch
-
Push your work back up to your fork
-
Submit a Pull Request so that we can review your changes
NOTE: Be sure to rebase the latest changes from "upstream" before making a pull request!
Module Versioning
This Module follows the principles of Semantic Versioning (SemVer).
Using the given version number of MAJOR.MINOR.PATCH, we apply the following constructs:
- Use the
MAJORversion for incompatible changes. - Use the
MINORversion when adding functionality in a backwards compatible manner. - Use the
PATCHversion when introducing backwards compatible bug fixes.
Backwards compatibility in 0.0.z and 0.y.z version
- In the context of initial development, backwards compatibility in versions
0.0.zis not guaranteed whenzis increased. (Initial development) - In the context of pre-release, backwards compatibility in versions
0.y.zis not guaranteed whenyis increased. (Pre-release)
Copyright
Copyright Β© 2018-2021 Hadenlabs
Trademarks
All other trademarks referenced herein are the property of their respective owners.
License
The code and styles are licensed under the LGPL-3.0 license See project license..
