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

Not possible to configure weekly auto scan for Registry Integrations #271

Open
vini-ppro opened this issue Sep 13, 2024 · 0 comments
Open

Comments

@vini-ppro
Copy link

For a registry integration, it is possible to configure weekly auto scan of images, for example:

image

The terraform provider does not support the same granularity of settings, for example configuring weekly scans. Among the various parameters offered by the provider, none of them allow for the specification of weekly scans on Tuesdays, for example:

  auto_pull                     = true
  auto_pull_interval            = 1
  auto_pull_max                 = 100
  auto_pull_rescan              = false
  auto_pull_time                = "08:45"

By configuring a registry integration via the UI, configuring weekly scans, and inspecting it via the API I see the following configuration:

    "auto_scan_time": {
        "time": "2024-06-04T14:45:00+02:00",
        "iteration": 1,
        "week_days": [
            "Tuesday"
        ],
        "auto_pull_day": 1,
        "iteration_type": "week"
    },

The parameter auto_scan_time is currently not supported by the provider

Affected Resource(s)

Please list the resources as a list, for example:

  • aquasec_integration_registry

Expected Behavior

The provider should implement the auto_scan_time parameter, similar as for the Aqua API, and allow for granular configuration of auto-scans, for example we scan images every Tuesdays at 00:000.

Actual Behavior

It is not possible to configure auto scans as granular as it is possible via the UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant