Repository files navigation

Terraform module to provision an github iam.

This is a list of plugins that need to be installed previously to enjoy all the goodies of this configuration:

• Pyenv
• Docker
• python
• taskfile

module"main" {source="hadenlabs/iam/github"version="0.2.1"providers={      github= github    }team={"name"="name-team""description ="team description""privacy" ="closed"    }    maintainers = ["user-github"]    members     = ["user-github"]  }

Full working examples can be found inexamples folder.

module"main" {source="hadenlabs/iam/github"version="0.2.1"providers={        github= github      }team={"name"="name-team""description ="team description""privacy" ="closed"      }      maintainers = ["user-github"]      members     = ["user-github"]  }

module"main" {source="hadenlabs/iam/github"version="0.2.1"providers={        github= github      }team={"name"="name-team""description ="team description""privacy" ="closed"      }      permissions = [        {          repository ="name repository",          permission ="pull",        },      ]      maintainers = ["user-github"]      members     = ["user-github"]  }

No modules.

list(object({
 repository = string
 permission = string
 }))

object({
 name = string
 description = string
 privacy = string
 })

Got a question?

File a GitHubissue.

Please use theissue tracker to report any bugs or file feature requests.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

1. Fork the repo on GitHub

2. Clone the project to your own machine

3. Commit changes to your own branch

4. Push your work back up to your fork

5. Submit aPull Request so that we can review your changes

NOTE: Be sure to rebase the latest changes from "upstream" before making a pull request!

This Module follows the principles ofSemantic Versioning (SemVer).

Using the given version number ofMAJOR.MINOR.PATCH, we apply the following constructs:

1. Use theMAJOR version for incompatible changes.
2. Use theMINOR version when adding functionality in a backwards compatible manner.
3. Use thePATCH version when introducing backwards compatible bug fixes.

• In the context of initial development, backwards compatibility in versions0.0.z isnot guaranteed whenz is increased. (Initial development)
• In the context of pre-release, backwards compatibility in versions0.y.z isnot guaranteed wheny is increased. (Pre-release)

Copyright © 2018-2021Hadenlabs

All other trademarks referenced herein are the property of their respective owners.

The code and styles are licensed under the LGPL-3.0 licenseSee project license..

Your feedback is appreciated