Add multi-application support with backward compatibility

[Copilot]

Enables managing feature flags for multiple applications from a single service instance. Each application gets independent namespace, storage backend, configmap settings, and workload restart configuration.

Changes

Protocol & Service

• Extended feature.proto with application field in Key and KeyValue messages
• Added GetApplications RPC to list configured applications
• Created application.Manager to orchestrate multiple persistence backends per application
• FeatureService routes operations to application-specific persistence based on context
• Legacy single-application mode preserved when APPLICATIONS env var not set

CLI

• Added -a/--application flag to all feature commands (get, set, delete, preset, getall)
• Added applications command to list available applications
• Default application selection via --default-application flag or DEFAULT_APPLICATION env var
• Commands default to first application if -a not specified

Helm Chart

• service.applications array in values.yaml for multi-app configuration
• ConfigMap template generates per-application env vars (APP_NAME_* prefix pattern)
• RBAC uses ClusterRole with RoleBindings per namespace instead of single Role
• CLI ConfigMap includes default application configuration

Configuration Example

service:
  applications:
    - name: yasm-frontend
      namespace: frontend
      storageType: configmap
      configMap:
        name: yasm-frontend
        preset: BANNER=Hello
        editable: BANNER
      workload:
        enabled: true
        type: deployment
        name: yasm-frontend
    - name: yasm-backend
      namespace: backend
      storageType: configmap
      configMap:
        name: yasm-backend
        preset: AUTH_ENABLED=true,BACKGROUND=blue
        editable: BACKGROUND
  defaultApplication: yasm-frontend

CLI usage:

feature-cli applications
feature-cli -a yasm-frontend set BANNER "Welcome"
feature-cli -a yasm-backend get AUTH_ENABLED

Backward Compatibility

Single-application deployments continue working without configuration changes. Multi-app mode activates only when service.applications array is populated or APPLICATIONS env var is set.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)
• invalid
  • Triggering command: /tmp/go-build1578093272/b432/delete.test /tmp/go-build1578093272/b432/delete.test -test.testlogfile=/tmp/go-build1578093272/b432/testlog.txt -test.paniconexit0 -test.timeout=10m0s /tmp/go-build2481619343/b759/vet.cfg g_.a pi@v0.35.0/flowc-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet o d/storagemigrati-atomic mpile ux-amd64/pkg/too-buildtags -qui�� lktS7eVtz pi@v0.35.0/netwo-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet /tmp/go-build312/home/REDACTED/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.6.linux-amd64/pkg/tool/linux_amd64/vet y/v1 mpile ux-amd64/pkg/too-buildtags (dns block)
  • Triggering command: /tmp/go-build1578093272/b435/get.test /tmp/go-build1578093272/b435/get.test -test.testlogfile=/tmp/go-build1578093272/b435/testlog.txt -test.paniconexit0 -test.timeout=10m0s /tmp/go-build2481619343/b768/vet.cfg g_.a pi@v0.35.0/rbac/-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet . ce/service/meta/-atomic mpile ux-amd64/pkg/too-buildtags -I 7thZhKWO9 pi@v0.35.0/resou-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet --gdwarf-5 v1beta1 mpile ux-amd64/pkg/too-buildtags (dns block)
  • Triggering command: /tmp/go-build1578093272/b438/getall.test /tmp/go-build1578093272/b438/getall.test -test.testlogfile=/tmp/go-build1578093272/b438/testlog.txt -test.paniconexit0 -test.timeout=10m0s /tmp/go-build2481619343/b763/vet.cfg g_.a pimachinery@v0.3-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet . rs/otlp/otlplog/-atomic mpile xAdz0IxsoYJo -I MnGS8ZYr_ pi@v0.35.0/stora-ifaceassert ux-amd64/pkg/tool/linux_amd64/vet --gdwarf-5 /pkg/apis/client-atomic mpile ux-amd64/pkg/too-buildtags (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support for multiple applications</issue_title>
<issue_description>I would like to be able to configure multiple applications like this

service:
  applications:
    - name: yasm-frontend
      namespace: frontend
      storageType: configmap # or in memory
      configMap:
        name: yasm-frontend
        preset: BANNER=Hello
        editable: BANNER
      workload: # for restarting a workload
        enabled: true
        type: deployment # Type of the workload
        name: yasm-frontend # Type of the workload
    - name: yasm-backend
      namespace: backend
      storageType: configmap
      configMap:
        name: yasm-backend
        preset: AUTH_ENABLED=true,BACKGROUND=blue
        editable: BACKGROUND

So basically the same functionality, but with the difference, that multiple applications can be configured. The CLI should have the name -a or --application flag and be able to receive the list of applications, like

feature-cli applicaitons
feature-cli -a yasm-frontend getable
feature-cli -a yasm-backend set BANNER "Hello, World"

There should be also an argument called --default-application or DEFAULT_APPLICATION, that is used if no application is specified.

The RBAC needs allow operations on multiple namespaces.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Support for multiple applications #58

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.