Skip to content

fix: update imports for environments v0.7.5's package reorg - #97

Merged
ntlaletsi70 merged 1 commit into
developfrom
fix/environments-v0.7.5-imports
Jul 19, 2026
Merged

fix: update imports for environments v0.7.5's package reorg#97
ntlaletsi70 merged 1 commit into
developfrom
fix/environments-v0.7.5-imports

Conversation

@ntlaletsi70

Copy link
Copy Markdown
Collaborator

What

Bumps github.com/blanketops/environments v0.7.2 → v0.7.5 and updates every import path affected by that release's package reorg (flat per-domain files → subpackages under core/, resolution/<domain>/resolve, pkg/secrets/{git,registry,github}/<consumer>, pkg/intent/{package,deployment}).

Why

environments v0.7.5 restructured most of the library into subpackages (see commit message for the full old→new mapping). Without this, environments-controller doesn't compile at all against v0.7.5.

Two real (non-mechanical) API changes came along with the reorg and needed actual code fixes, not just import-path updates:

  • github.NewGitHubProviderSecretReconciler gained a storeKind parameter, matching every other reconciler's signature.
  • GitHubEvent resolution dropped its proto-style Contract wrapper (ToGitHubEventContract().GetEventId() etc.) for plain string fields directly on ResolvedGitHubEventSpec (EventID, EventType, Ref, CommitSHA) — updated the build-observer and githubevent-observer call sites accordingly.

Domain

  • environments
  • events
  • sources
  • networks
  • common
  • Application / domain layer (no API surface change)
  • CI / tooling / docs

API impact

  • No API surface change

Checklist

  • go build ./..., go vet ./..., gofmt -l all pass clean
  • mage verify — no mage target in this repo; substituted the above
  • buf breaking — not applicable, no proto contract changes here
  • Panic-free resolution — no panic() calls added
  • Import paths — no gen/go/blanketops/... contract types touched
  • BlanketOps labels — unaffected
  • Conditions/events — unaffected, only import paths and two call-site signature fixes changed
  • ESP-0001 — no contract semantics changed
  • Commit messages follow Conventional Commits

Notes for reviewer

No test files exist in this repo currently (tracked as a follow-up — coverage work is starting next, scoped to domains/mediators/cache, not the controller-runtime wiring layer).

Bumps github.com/blanketops/environments v0.7.2 -> v0.7.5, which
restructured most of the library from flat per-domain files into
subpackages:

  - core                        -> core/{cache,command,conditions,
                                    domain,engine,events,predicates,
                                    registry}
  - resolution/<domain>          -> resolution/<domain>/resolve
  - pkg/secrets/{git,registry,
    github}                      -> one subpackage per consumer
                                    (e.g. pkg/secrets/git/build,
                                    pkg/secrets/git/deployment,
                                    pkg/secrets/git/fluxcd, ...)
  - pkg/apis/packages/intent     -> pkg/intent/package
  - pkg/apis/deployment/api's
    NewRuntimeProvider,
    NewReconciliationExecutor    -> pkg/apis/deployment/strategy,
                                     pkg/apis/deployment/reconcile
  - pkg/apis/deployment/
    application.NewIntentBuilder -> pkg/intent/deployment

Also two real (non-mechanical) API changes along the way:
  - github.NewGitHubProviderSecretReconciler gained a storeKind
    parameter, matching every other reconciler's signature.
  - GitHubEvent resolution dropped its proto-style Contract wrapper
    (ToGitHubEventContract().GetEventId() etc.) in favor of plain
    string fields directly on ResolvedGitHubEventSpec (EventID,
    EventType, Ref, CommitSHA) — call sites in the build-observer and
    githubevent-observer updated accordingly.

Where a subpackage name collided with an existing import in the same
file (core/events vs k8s.io/client-go/tools/events; the new
pkg/intent/deployment package named `deployment` vs this repo's own
internal/mediators/deployment import), the new import is aliased
rather than renaming the existing one, to minimize the diff.

go build ./..., go vet ./..., and gofmt all pass clean. No test files
exist in this repo to run.
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.

1 participant