Skip to content

chore: merge upstream m-cmp/main into develop - #88

Open
dogfootman wants to merge 35 commits into
developfrom
chore/sync-upstream-main
Open

dogfootman wants to merge 35 commits into
developfrom
chore/sync-upstream-main

Conversation

@dogfootman

Copy link
Copy Markdown
Collaborator

목적

업스트림(m-cmp/main)을 develop에 먼저 머지해, 이후 develop → m-cmp/main 동기화 PR이 충돌 없이 올라가도록 합니다.

충돌 1건 해소

conf/docker/conf/mc-iam-manager/permission.yamldevelop 측 채택

  • 업스트림 fix: grant workflow submenu permissions m-cmp/mc-admin-cli#199(fix: grant workflow submenu permissions)가 구 메뉴 id 목록에 mcworkflows, mceventlistener를 추가했는데, develop에는 두 항목이 이미 있습니다. #199의 의도는 보존됩니다.
  • develop 쪽은 재정의된 메뉴 카탈로그에 맞춰 permission seed를 정리한 상태입니다. 업스트림에만 있던 id 19개 중 17개는 현재 webconsole_menu_resources.yaml에 존재하지 않는 구 id(observabilitymcobservability, images/specsserverimages/serverspecs 등 rename 및 폐기)라 제거가 정상입니다.

검토 필요 — viewer 역할 권한 축소

업스트림에만 있던 id 19개 중 settings, environment 2개는 현재 메뉴 카탈로그에 살아 있습니다. 이 둘이 빠지는 역할은 viewer 하나뿐입니다.

메뉴
upstream viewer operations, analytics, observability, settings, environment, cloudrescatalogs
develop viewer operations, analytics, mcobservability, mco11ymonitorings, mc011ylogs, mc011yinsight, mc011ytracing

admin, operatorsettings/environment를 그대로 유지합니다. viewer에서 뺀 것이 의도된 축소인지 확인 부탁드립니다. 의도와 다르면 이 PR에서 두 줄 추가하면 됩니다.

이미지 태그 병합 결과

업스트림이 앞서 있던 태그가 모두 반영되고, develop이 앞서 있던 태그는 유지됩니다.

이미지 결과 출처
cb-spider / cb-tumblebug 0.13.2 upstream
cb-mapui 0.13.6 upstream
mc-costopti-* (13개) 0.6.3 upstream
mc-observability-* (9개) 0.6.1 upstream
mc-application-manager / mc-workflow-manager 0.6.2 upstream
mc-iam-manager 0.6.3 develop
mc-web-console-api / front 0.6.5 develop

검증

  • docker compose --env-file .env.setup config 통과
  • permission.yaml YAML 파싱 정상 (역할 5개: admin, billadmin, billviewer, operator, viewer)
  • 충돌 마커 잔존 없음
  • 머지 후 upstream/main이 이 브랜치에 완전 포함됨 확인

ddihn and others added 30 commits July 29, 2026 10:28
Added environment variables for OPENBAO configuration and S3 region.
Removed timezone setting for the mc-cost-optimizer service.
Added timezone setting for containers in docker-compose.
BE now needs to call azure-vm-rightsizer, ncp-vm-rightsizer, and
gcpCollector directly for on-demand batch triggers, but only
costcollector/costprocessor/costselector URLs were wired.

- add MC_COST_OPTIMIZER_AZURE_RIGHTSIZER_URL / NCP_RIGHTSIZER_URL
- fix MC_COST_OPTIMIZER_COST_GCP_COLLECTOR_URL hostname (pointed at
  mc-cost-optimizer-cost-gcp-collector, a container that doesn't
  exist; the real service is mc-cost-optimizer-gcp-collector)
- wire all three into mc-cost-optimizer-be's environment
latest currently resolves to 12.3.2 anyway (same digest, verified via
docker pull), so this only removes the drift risk on future redeploys -
no behavior change today.
…alarm URLs

- costopti.azurecollector.url / costopti.ncpcollector.url: BE needs
  these to trigger Azure/NCP budget checks on demand, only
  azurerightsizer/ncprightsizer/gcpcollector were wired.
- ALARM_SERVICE: costCollector's application.properties expects this
  env var (costopti.alarmservice.url=${ALARM_SERVICE:alarm_service})
  but it was never set here, so AWS budget alarms failed with
  "URI is not absolute" trying to reach the literal string
  "alarm_service" instead of a real URL.

Both env vars (MC_COST_OPTIMIZER_COST_AZURE_COLLECTOR_URL,
MC_COST_OPTIMIZER_COST_NCP_COLLECTOR_URL, MC_COST_OPTIMIZER_ALARM_URL)
already existed in .env.setup - just weren't wired into these services.
Update MC-Cost-Optimizer Docker images to version 0.6.3
Signed-off-by: Seokho Son <shsongist@gmail.com>
sync: installAll wave startup/monitoring, cleanAll image-keep option, nginx/iam fixes
Signed-off-by: Seokho Son <shsongist@gmail.com>
sync: mc-iam-manager/mc-web-console 0.6.2 bump, cli verbose-log fix
Signed-off-by: Seokho Son <shsongist@gmail.com>
fix: secure jenkins access and wait for plugin initialization
chore: bump mc-observability to 0.6.1 and sync agent ansible files
feat: bootstrap Jenkins object storage credentials securely
st-yclee and others added 5 commits September 7, 2026 17:58
fix: grant workflow submenu permissions
Resolve conf/docker/conf/mc-iam-manager/permission.yaml by keeping the
develop side. Upstream m-cmp#199 added mcworkflows/mceventlistener to the old
menu id list; develop already grants both, on top of a rework that aligns
the permission seed with the redefined menu catalog. 17 of the ids only
present upstream no longer exist in webconsole_menu_resources.yaml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants