Closed brackend closed 3 months ago
I don't believe those are valid here - those would be provided in your repository when you create your cluster definition using this module
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.
Is your request related to a problem? Please describe.
Gitlab can mirror public repos. Gitlab has a build in template for scanning and creating terraform module in registry format with the same project. Users can then "source" the module and "version" in parent code. The problem is, adding a ci template file breaks the mirror.
Describe the solution you'd like.
would it be possible to add .gitlab-ci.yml. See content below.
This would automatically scan and generate a terraform module in gitlab.
The template is built into gitlab.
Describe alternatives you've considered.
Not aware of any. Adding a .gitlab-ci.yml to a mirrored repo will break the mirror on gitlab. Not sure if there is another way of running a pipeline for the project to create the terraform module without adding a ci file directly to the branch.
Additional context
` include:
stages:
fmt: extends: .terraform-module:fmt
See the included job template at
Terraform/Module-Base.gitlab-ci.yml
to learn about supported variables.deploy: extends: .terraform-module:deploy rules:
`