You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refs sparkfabrik-innovation-team/board#3833: Update changelog, README, and configuration files for version 1.0.0 release, including new variables and breaking changes
Copy file name to clipboardExpand all lines: CHANGELOG.md
+18-20Lines changed: 18 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,41 +10,39 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
10
10
11
11
## [1.0.0] - 2025-10-02
12
12
13
-
[Compare with previous version](https://github.com/sparkfabrik/terraform-gitlab-kubernetes-gitlab-agent/compare/1.0.0...0.13.0)
13
+
[Compare with previous version](https://github.com/sparkfabrik/terraform-gitlab-kubernetes-gitlab-agent/compare/0.13.0...1.0.0)
14
14
15
15
### Added
16
16
17
-
- 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`
18
-
- New variable `groups_enabled` to specify groups where the GitLab Agent should be enabled (when not operating at root group level)
19
-
- New variable `projects_enabled` to specify projects where the GitLab Agent should be enabled (when not operating at root group level)
20
-
- Auto-detection of parent group when `operate_at_root_group_level = false` and no groups/projects are specified
21
-
- Support for creating CI/CD variables in multiple groups and projects simultaneously
22
-
- Dynamic generation of agent configuration file based on enabled groups/projects using `yamlencode()`
23
-
- New outputs: `gitlab_enabled_groups`, `gitlab_enabled_projects`, `gitlab_parent_group_auto_detected`, `operate_at_root_group_level`
17
+
- 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`.
18
+
- New variable `groups_enabled` to specify groups where the GitLab Agent should be enabled (when not operating at root group level).
19
+
- New variable `projects_enabled` to specify projects where the GitLab Agent should be enabled (when not operating at root group level).
20
+
- Auto-detection of parent group when `operate_at_root_group_level = false` and no groups/projects are specified.
21
+
- Support for creating CI/CD variables in multiple groups and projects simultaneously.
22
+
- Dynamic generation of agent configuration file based on enabled groups/projects using `yamlencode()`.
23
+
- New outputs: `gitlab_enabled_groups`, `gitlab_enabled_projects`, `gitlab_parent_group_auto_detected`.
24
24
25
25
### Changed
26
26
27
-
- Agent configuration file is now dynamically generated based on `operate_at_root_group_level` and enabled groups/projects
28
-
- CI/CD variables can now be created in multiple targets (root group, specific groups, or specific projects) depending on configuration
29
-
- Output `gitlab_root_namespace_id` now returns `null` when not operating at root group level
30
-
- User access (`user_access`) is now controlled directly by `operate_at_root_group_level` and only granted when operating at root group level
27
+
- Agent configuration file is now dynamically generated based on `operate_at_root_group_level` and enabled groups/projects.
28
+
- CI/CD variables can now be created in multiple targets (root group, specific groups, or specific projects) depending on configuration.
29
+
- Output `gitlab_root_namespace_id` now returns `null` when not operating at root group level.
31
30
32
31
### Removed
33
32
34
-
-**BREAKING CHANGE**: Variable `gitlab_agent_grant_user_access_to_root_namespace` - functionality is now controlled by `operate_at_root_group_level`
35
-
-**BREAKING CHANGE**: Variable `gitlab_agent_grant_access_to_entire_root_namespace` - replaced by `operate_at_root_group_level`
36
-
-**BREAKING CHANGE**: Variable `gitlab_agent_create_variables_in_root_namespace` - behavior is now determined by `operate_at_root_group_level`
37
-
- Backward compatibility logic for deprecated variables
33
+
-**BREAKING CHANGE**: variable `gitlab_agent_grant_access_to_entire_root_namespace` - replaced by `operate_at_root_group_level`.
34
+
-**BREAKING CHANGE**: variable `gitlab_agent_create_variables_in_root_namespace` - behavior is now determined by `operate_at_root_group_level`.
35
+
- Backward compatibility logic for deprecated variables.
38
36
39
37
### Migration Guide
40
38
41
39
If you were using the removed variables, migrate as follows:
**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.
45
+
**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.
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ It uses the Gitlab provider to register the agent on the Gitlab server. The gene
6
6
7
7
The module supports multiple configuration modes:
8
8
9
-
-**Root Group Level** (default): The agent has access to the entire root namespace and CI/CD variables are created in the root group
10
-
-**Auto-detect Parent**: When not operating at root level and no specific groups/projects are provided, the module automatically detects the parent group of the agent project
11
-
-**Specific Groups/Projects**: Enable the agent only for specific groups or projects, with variables created in those locations
9
+
-**Root Group Level** (default): The agent has access to the entire root namespace and CI/CD variables are created in the root group.
10
+
-**Auto-detect Parent**: when not operating at root level and no specific groups/projects are provided, the module automatically detects the parent group of the agent project.
11
+
-**Specific Groups/Projects**: enable the agent only for specific groups or projects, with variables created in those locations.
12
12
13
13
**ATTENTION**: you have to manually create the project that will host the Gitlab Agent configuration in Gitlab before running this module.
description="Grant `user_access` to the root namespace."
42
+
type=bool
43
+
default=false
44
+
}
45
+
40
46
variable"groups_enabled" {
41
47
description="List of group paths where the GitLab Agent should be enabled. Only used when operate_at_root_group_level is false. If empty and projects_enabled is also empty, the parent group of the agent project will be used automatically."
42
48
type=list(string)
@@ -50,14 +56,14 @@ variable "projects_enabled" {
50
56
}
51
57
52
58
variable"gitlab_agent_append_to_config_file" {
53
-
description="Append the Gitlab Agent configuration to the configuration file created for the entire root namespace. This variable is only used when `gitlab_agent_grant_access_to_entire_root_namespace` is true."
59
+
description="Append custom configuration to the Gitlab Agent configuration file. This content will be added at the end of the generated configuration."
description="The content of the Gitlab Agent configuration file. If not provided and `gitlab_agent_grant_access_to_entire_root_namespace` is true, the default configuration file will be used and the root namespace will be granted access to the Gitlab Agent. If you set this variable, it takes precedence over `gitlab_agent_grant_access_to_entire_root_namespace`."
66
+
description="The content of the Gitlab Agent configuration file. If not provided, the default configuration file will be generated based on `operate_at_root_group_level`, `groups_enabled`, and `projects_enabled`. If you set this variable, it takes precedence over the automatic configuration generation."
0 commit comments