You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider removing the support for older packet-ccm cloud provider entirely, only supporting cloud-provider-equinix-metal (equinixmetal prefix). The method of introspection we used to figure out which cloud provider folks had installed:
Doesn't work with the newer controller runtime code
Is a bit of a hack where we had to swallow client errors to get it to work
Would require a lot of weird refactoring and eating of wrapped errors to work now
Doesn't seem needed at this point as who is even using the older packet-ccm at this point?
Is not how upstream docker handles it (they just set providerid prefix to docker:////) or another provider like azure handles it (they just straight up go with the UUID and no prefix, it seems).
Consider removing the support for older packet-ccm cloud provider entirely, only supporting cloud-provider-equinix-metal (equinixmetal prefix). The method of introspection we used to figure out which cloud provider folks had installed:
Originally posted by @cprivitere in #674 (comment)
The text was updated successfully, but these errors were encountered: