1.2.0

What's Changed

• feat: disable autoassign current user by default by @FabrizioCafolla in #25

Full Changelog: 1.1.0...1.2.0

1.1.0

What's Changed

• refs platform/board#3920: check if membership exist by @FabrizioCafolla in #24
• refs platform/board#3920: add GitLab provider user as Maintainers of project by @FabrizioCafolla in #23

Full Changelog: 1.0.0...1.1.0

1.0.0

Compare with previous version

Added

• New variable operate_at_root_group_level to simplify configuration and replace the combination of gitlab_agent_grant_access_to_entire_root_namespace and gitlab_agent_create_variables_in_root_namespace.
• New variable groups_enabled to specify groups where the GitLab Agent should be enabled (when not operating at root group level).
• New variable projects_enabled to specify projects where the GitLab Agent should be enabled (when not operating at root group level).
• Auto-detection of parent group when operate_at_root_group_level = false and no groups/projects are specified.
• Support for creating CI/CD variables in multiple groups and projects simultaneously.
• Dynamic generation of agent configuration file based on enabled groups/projects using yamlencode().
• New outputs: gitlab_enabled_groups, gitlab_enabled_projects, gitlab_parent_group_auto_detected.

Changed

• Agent configuration file is now dynamically generated based on operate_at_root_group_level and enabled groups/projects.
• CI/CD variables can now be created in multiple targets (root group, specific groups, or specific projects) depending on configuration.
• Output gitlab_root_namespace_id now returns null when not operating at root group level.

Removed

• BREAKING CHANGE: variable gitlab_agent_grant_access_to_entire_root_namespace - replaced by operate_at_root_group_level.
• BREAKING CHANGE: variable gitlab_agent_create_variables_in_root_namespace - behavior is now determined by operate_at_root_group_level.
• Backward compatibility logic for deprecated variables.

Migration Guide

If you were using the removed variables, migrate as follows:

• gitlab_agent_grant_user_access_to_root_namespace = true -> operate_at_root_group_level = true + gitlab_agent_grant_user_access_to_root_namespace = true
• gitlab_agent_grant_access_to_entire_root_namespace = true + gitlab_agent_create_variables_in_root_namespace = true → operate_at_root_group_level = true + gitlab_agent_grant_user_access_to_root_namespace = true
• gitlab_agent_grant_access_to_entire_root_namespace = false -> operate_at_root_group_level = false + configure groups_enabled and/or projects_enabled

Note: user access is now only available when operate_at_root_group_level = true. If you need user access to specific groups/projects, this is not currently supported by Gitlab.

0.13.0

What's Changed

• refs platform/3672: upgrade gitlab agent by @Syphon83 in #20

Full Changelog: 0.12.0...0.13.0

0.12.0

What's Changed

• chore(deps): update dependency terraform_docs_makefile to v0.20.0 by @renovate in #16
• feat: add gitlab_agent_enabled_deploy variable to control whether GitLab Agent components are deployed by @filippolmt in #18
• fix: CHANGELOG by @filippolmt in #19

New Contributors

• @filippolmt made their first contribution in #18

Full Changelog: 0.11.0...0.12.0

0.11.0

What's Changed

• refa platform/3565: upgrade agent to 17.10.0 by @Syphon83 in #17

Full Changelog: 0.10.0...0.11.0

0.10.0

Compare with previous version

Changed

• Upgrade the default Helm chart to version 2.11.0.

0.9.0

Compare with previous version

Changed

• Upgrade the default Helm chart to version 2.8.3.

0.8.0

Compare with previous version

Changed

• Upgrade the default Helm chart to version 2.8.2.

0.7.0

Compare with previous version

Added

• The module can create the gitlab agents project by setting the variable gitlab_project_name.