Setting these new fields as required may break existing packages using agentless, do we have any?

Not at them moment, and not even the CSPM integration. AFAIK there are some integrations like Okta and Cloud Connector that want to use this setting.

@eyalkraft can you confirm?

The search connectors integration is already merged

• Elastic connector integration integrations#10898

The Okta one is on hold

• [okta] Enable Agentless deployment integrations#11116

@jsoriano How could we still make these fields required? Can the integrations be updated first? Or could we provide a default value?

How could we still make these fields required? Can the integrations be updated first? Or could we provide a default value?

We cannot update the integrations first because the field is not allowed yet. We have two options:

• We add the fields as now, but we make them mandatory only for packages using spec >= 3.2.3. Then integrations can add the fields, but they are only required on newer versions of the spec. This would be the less "breaking" approach, but we can have packages with older versions of the spec and without these fields, what would need to be handled by agentless code.
• We make the breaking change, so these fields are required. Then when updating the package-spec in the integrations repository, we need to add the fields where they are missing. This option is more "breaking", but probably better in the long term, but we need to know what fields to use when updating the package-spec.

Regarding default fields, we can add a default to the spec as documentation, but its implementation depends on whatever reads these settings, defaults are not enforced by the spec.

@jsoriano, I had an offline conversation with @eyalkraft, we decided to change all 3 integrations that have or will have the depoyment_mode attribute.