Implement unique project name validation in Digger configuration #1767
+72
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1309
This PR implements a crucial feature to ensure that project names in the Digger configuration (digger.yml) are unique. This is an important prerequisite for proper functionality, as Digger relies on project names to organize various resources, including state files.
Key Changes to Digger Configuration
1. Updated ValidateDiggerConfigYaml function in
libs/digger_config/yaml.go
:2. Modified ConvertDiggerYamlToConfig function in
libs/digger_config/converters.go
:3. Added a new test case
TestDiggerConfigDuplicateProjectNames
inlibs/digger_config/digger_config_test.go
:4. Updated Documentation in
docs/ce/reference/digger.yml.mdx
:name
field must be unique across all projects.Please review these changes and let me know if any further modifications or clarifications are needed.