All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- feat: disable autoassign current user by default
- refs platform/board#3920: add GitLab provider user as Maintainers of
local.project_idproject.
- New variable
operate_at_root_group_levelto simplify configuration and replace the combination ofgitlab_agent_grant_access_to_entire_root_namespaceandgitlab_agent_create_variables_in_root_namespace. - New variable
groups_enabledto specify groups where the GitLab Agent should be enabled (when not operating at root group level). - New variable
projects_enabledto 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 = falseand 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.
- Agent configuration file is now dynamically generated based on
operate_at_root_group_leveland 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_idnow returnsnullwhen not operating at root group level.
- BREAKING CHANGE: variable
gitlab_agent_grant_access_to_entire_root_namespace- replaced byoperate_at_root_group_level. - BREAKING CHANGE: variable
gitlab_agent_create_variables_in_root_namespace- behavior is now determined byoperate_at_root_group_level. - Backward compatibility logic for deprecated variables.
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 = truegitlab_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 = truegitlab_agent_grant_access_to_entire_root_namespace = false->operate_at_root_group_level = false+ configuregroups_enabledand/orprojects_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.
- Add the
gitlab_agent_deploy_enabledvariable to control whether to deploy the GitLab Agent components. When set to false, the module only creates the GitLab Agent token, Kubernetes namespace and secret without deploying the agent itself.
- Upgrade the default Helm chart to version
2.13.0.
- Upgrade version gitlab-agent Helm chart to
2.11.0.
- Upgrade the default Helm chart to version
2.8.3.
- Upgrade the default Helm chart to version
2.8.2.
- The module can create the gitlab agents project by setting the variable
gitlab_project_name.
- Upgrade the default Helm chart to version
2.6.2.
- Add the
gitlab_agent_grant_user_access_to_root_namespacevariable to grant theuser_accesspermission on the root namespace. - Upgrade the Helm chart to version
2.5.0for Gitlab 17.
- Add the
gitlab_agents_project_idandgitlab_root_namespace_idoutputs to allow the retrieval of the Gitlab project and root namespace IDs.
- Add the
create_default_pod_anti_affinityvariable to allow the creation of the default podAntiAffinity rule in the helm values.
- Add dependency on the Gitlab variables to prevent their creation before the helm release.
- Add the
gitlab_agent_append_to_config_filevariable to allow customizations to the agent configuration file keeping the access for the root namespace managed by the module.
- First release.