Skip to content

Commit

Permalink
Use library-go ApplyDeployment and ApplyDaemonset
Browse files Browse the repository at this point in the history
Our current functions in ./lib are out of date and we should be using
library-go instead

The library-go functions require passing the generation of the
previously applied deployment/daemonset, and this should be stored on an
MCO CRD. Because this currently doesn't exist, the existing generation
is passed as generation. This is no worse than how MCO's current
functions work, so the library-go functions should still be used until
an MCO CRD is created.

Files with the now unused functions and unused helper functions were
removed:
resourceapply/apps.go
resourcemerge/{apps.go,apps_test.go,core.go,core_test.go}

Helps openshift#819
  • Loading branch information
mkenigs committed Jan 31, 2022
1 parent 907f11c commit e65917a
Show file tree
Hide file tree
Showing 6 changed files with 16 additions and 887 deletions.
52 changes: 0 additions & 52 deletions lib/resourceapply/apps.go

This file was deleted.

45 changes: 0 additions & 45 deletions lib/resourcemerge/apps.go

This file was deleted.

147 changes: 0 additions & 147 deletions lib/resourcemerge/apps_test.go

This file was deleted.

Loading

0 comments on commit e65917a

Please sign in to comment.