Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable registry tests #531

Merged
merged 1 commit into from
Dec 12, 2024
Merged

enable registry tests #531

merged 1 commit into from
Dec 12, 2024

Conversation

refaelm92
Copy link
Contributor

@refaelm92 refaelm92 commented Dec 12, 2024

User description

Signed-off-by: refaelm [email protected]


PR Type

Enhancement


Description

  • Enabled registry scanning tests by updating target repositories configuration
  • Replaced dummy repository names with actual repository names:
    • cadashboardbe-dummycadashboardbe
    • event-ingester-service-dummyevent-ingester-service

Changes walkthrough 📝

Relevant files
Configuration changes
system_test_mapping.json
Update registry scanning test configuration                           

system_test_mapping.json

  • Updated target repositories for registry scanning tests
  • Changed from dummy repositories to actual repositories
    ('cadashboardbe' and 'event-ingester-service')
  • +2/-2     

    💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

    Signed-off-by: refaelm <[email protected]>
    Copy link

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 PR contains tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Configuration Change
    Verify that the new repository names are correct and accessible in the target environment

    Copy link

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Score
    Security
    Add environment restrictions to prevent test operations from affecting production systems

    Consider adding a skip condition for production environments to protect production
    registries from test scanning operations.

    system_test_mapping.json [1233-1244]

     "test_registry_scanning": {
       "target": [
         "In cluster",
         "Backend"
       ],
       "target_repositories": [
         "cadashboardbe",
         "event-ingester-service"
       ],
       "description": "",
    -  "skip_on_environment": "",
    +  "skip_on_environment": "production,production-us",
       "owner": ""
     }
    • Apply this suggestion
    Suggestion importance[1-10]: 9

    Why: This is a critical security suggestion that prevents test scanning operations from potentially impacting production environments. The change aligns with the pattern seen in other tests in the file where production environments are explicitly skipped.

    9

    Copy link

    Failed to generate code suggestions for PR

    @refaelm92 refaelm92 merged commit b60f40c into master Dec 12, 2024
    3 checks passed
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants