Skip to content

Conversation

christophstrobl
Copy link
Member

Prior to this change regenerating repository code for eg. test execution caused trouble when trying to override existing json metadata files. We now back off in case of existing files and added an explicit config flag for users to opt out of having the metadata file being present in the target resources.

Resolves: #3354

Prior to this change regenerating repository instances for eg. test execution caused trouble when trying to override existing json metadata files. We now back off in case of existing files and added an explicit config flag for users to opt out of having the metadata file being present in the target resources.
Add renderers to format trace messages.
@mp911de mp911de added this to the 4.0 M6 (2025.1.0) milestone Sep 5, 2025
mp911de pushed a commit that referenced this pull request Sep 5, 2025
Prior to this change regenerating repository instances for eg. test execution caused trouble when trying to override existing json metadata files. We now back off in case of existing files and added an explicit config flag for users to opt out of having the metadata file being present in the target resources.

Original pull request: #3355
Closes #3354
mp911de added a commit that referenced this pull request Sep 5, 2025
Add renderers to format trace messages.

Original pull request: #3355
See #3354
@mp911de mp911de added the type: bug A general bug label Sep 5, 2025
@mp911de mp911de closed this Sep 5, 2025
@mp911de mp911de deleted the issue/3354 branch September 5, 2025 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AOT Repositories: OwnerRepository.json already exists
2 participants