Decision needed: exclude EdgeCloud from release automation

[hdamker]

Background

The EdgeCloud repository currently carries the sandbox-api-repository topic, which causes it to be included in all release automation tooling (Release Collector, bulk campaigns, centralized linting). However, EdgeCloud functions as an umbrella repository for the Edge Cloud sub-project and does not follow the standard API repository structure:

• No rX.Y releases (only legacy v0.9.3-rc, v0.8.1)
• Non-standard file layout (centralized linting cannot be applied, see admin: migrate to centralized linting workflows EdgeCloud#388)
• All individual APIs have already been split into dedicated repositories (SimpleEdgeDiscovery, TrafficInfluence, ApplicationEndpointDiscovery, ApplicationEndpointRegistration, OptimalEdgeDiscovery), which all participate in automation successfully
• One remaining API (Edge Application Management) is still in the umbrella repo; moving it to a dedicated repository has been discussed in admin: migrate to centralized linting workflows EdgeCloud#388

Automated campaigns consistently fail or produce incorrect results for this repository. In the recent release-plan rollout campaign, EdgeCloud was the only repository that failed out of 63.

Requested decision

Should the sandbox-api-repository topic be removed from EdgeCloud to exclude it from release automation?

The camara-sp-edge-cloud topic would remain, so the sub-project grouping is preserved. The 5 split-out repositories are unaffected and continue to work normally.

Details and context in the corresponding issue: camaraproject/EdgeCloud#408

[albertoramosmonagas]

Hi @hdamker, just when I was reviewing archived repositories, this was almost a proposal because there was no activity, but there were some recent open issues and the work had been moved to other repositories. Maybe it could be another new proposal for archiving and we could just leave the group name so that it continues to serve as an umbrella for the rest of the APIs?

[hdamker]

@albertoramosmonagas there is quite a lot of documentation etc in the repository, so I would leave it up to the team to keep the repository under the Sub Project umbrella (similar but not same as DeviceStatus and KnowYourCustomer). But I we can't continue to support it as an API Repository and from ReleaseManagement.

[tanjadegroot]

Release Management decision to exclude (not archive) this repo for now.
The team is recommended to ask for a separate repository for the Edge Application Management API .

[hdamker]

Removal of the topic sandbox-api-repository done. Closing the issue.