search

enterprise-contract / community

A repo for community utilization
https://enterprisecontract.dev
Apache License 2.0
0 stars 3 forks source link

Community Meeting January 31th, 2024 #25

Closed robnester-rh closed 8 months ago

robnester-rh commented 9 months ago

Overview At 10am Eastern, 7am Pacific, 2pm UTC; find your time

Video call link: https://meet.google.com/ved-ivnv-aen dial-in: (US) +1 409-444-2447‬ PIN: ‪873 550 579#‬ More phone numbers: tel.meet/ved-ivnv-aen?pin=7872592963542&hs=1

Add topics you'd like to discuss below!

lcarva commented 9 months ago

I'd like to discuss "acceptable bundles" as described here.

The list of acceptable bundles is time based. A bundle that is acceptable today is not necessarily acceptable tomorrow. The list below may contain bundles that are "too old" and no longer acceptable. The reason for this behavior is to allow users a certain period of time to upgrade to a newer bundle.

The concept of entries being "too old" is confusing, making it hard to get the implementation right, and even to explain how it is supposed to work for users.

To further complicate things, the complete feature is implemented partially in ec-cli and partially in ec-policies.

Maybe it's time to find an alternate approach?

(Also somewhat related to https://github.com/enterprise-contract/ec-cli/issues/1291)

lcarva commented 9 months ago

Should we move the CRD to the ec-cli repo?

Usually a CRD is paired with a controller (thus The Operator Pattern). We don’t have a controller. We may never will. In any case, the logic that interprets what a CRD means is implemented in the ec-cli repository. We have a pattern where we make a change to the CRD, then another change in a different repo to implement the functionality.

robnester-rh commented 7 months ago

Meeting recording: https://drive.google.com/file/d/14jX28MYZhUqdeu267aD35mRxsFfWUMmk/view?usp=drive_link