canonical / canonical/cos-proxy-operator

Improve status message when settling is taking too long

Open
#84 0 comments 0 reactions 0 assignees View on GitHub
Status: Triage Type: Enhancement
Dominant language
Python
Stars
3
Forks
12
PR merge metrics
No merged PRs in 30d

Description

### Enhancement Proposal

When deploying COS Proxy at scale, it takes quite a while for the units to settle if the proxy is related to COS prior to being related to the workloads.

This is easily resolved by changing the order of relating to wait for the proxy to settle prior to relating it to COS.

Currently, the status message is empty while the proxy is processing. This should be improved by setting a status message whenever it takes too long (>5m?) for it to settle.

It should also say that its prcessing proxied relations when that is the case

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or tests; start by locating the status-message handling and the proxied-relation processing entry points. Reproduce the deployment order where the proxy relates to COS before workloads, then verify that a long-running settlement reports processing and proxied relations instead of leaving the status empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.