[Atlassian Confluence] Add agentless support

[moxarth-rathod]

Proposed commit message

atlassian_confluence: add agentless support and update kibana version constraint

Adds support for agentless and updates the Kibana version constraint to avoid a known issue 
where selecting agentless deployment mode hides configuration fields and blocks 
deployment if inputs default to `enabled: false`.

Ref: https://github.com/elastic/kibana/pull/265106

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

• Clone integrations repo.
• Install the elastic package locally.
• Start the elastic stack using the elastic package.
• Move to integrations/packages/atlassian_confluence directory.
• Run the following command to run tests.

elastic-package test -v

Related issues

• Closes [atlassian_confluence] Add Agentless Deployment Support #18401

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[macroscopeapp]

🟡 Medium audit/manifest.yml:52

Removing enabled: false from the httpjson input causes it to default to enabled alongside the logfile input. Since api_url is required with no default, users who only want logfile collection will have an enabled httpjson input lacking required configuration, causing agent errors. The sibling Atlassian integrations (atlassian_jira, atlassian_bitbucket) retain enabled: false on their httpjson streams, suggesting this removal is inconsistent with the established pattern. Consider restoring enabled: false to keep httpjson opt-in.

   - input: httpjson
     title: Confluence audit logs via Confluence audit API
     description: Collect Confluence audit logs via Confluence audit API
+    enabled: false
     template_path: httpjson.yml.hbs

🤖 Copy this AI Prompt to have your agent fix this:

In file packages/atlassian_confluence/data_stream/audit/manifest.yml around lines 52-54:

Removing `enabled: false` from the `httpjson` input causes it to default to enabled alongside the `logfile` input. Since `api_url` is required with no default, users who only want logfile collection will have an enabled httpjson input lacking required configuration, causing agent errors. The sibling Atlassian integrations (`atlassian_jira`, `atlassian_bitbucket`) retain `enabled: false` on their httpjson streams, suggesting this removal is inconsistent with the established pattern. Consider restoring `enabled: false` to keep httpjson opt-in.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[kcreddy]

Waiting on clarification for path forward: #18141 (comment) and elastic/kibana#265106 (comment)

[efd6]

/test

[efd6]

Revert this placement to the original location to avoid the diff noise.

[kcreddy]

@moxarth-rathod this is still not done - it shows up in the diff.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[kcreddy]

LGTM, thanks!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 519ea5b

History

• 💚 Build #43934 succeeded 7d231db
• 💚 Build #42390 succeeded 7d231db
• 💚 Build #41650 succeeded 7d66129
• 💚 Build #41581 succeeded a2a695a

cc @moxarth-rathod

[elastic-vault-github-plugin-prod]

Package atlassian_confluence - 1.31.0 containing this change is available at https://epr.elastic.co/package/atlassian_confluence/1.31.0/