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
We are growing in RFEs, resource types and cloud providers. Looks like the current monolithic implementation for cleaning up resources wouldn't be sufficient and its very vast.
Its really filthy for increasing the cleanup scope of in terms of resource types, criterias etc.
Hence I would like to open the discussion with the community to help us decide on a design pattern that uses OOPs concepts for the betterment, and simplicity for developers to expand the horizon of cloudwash.
The Abstract classing / layer would really help to force some design pattern for all the cloud providers, criterias, resource types etc, but opening the floor here to hear from you all !!!!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello @ALL,
We are growing in RFEs, resource types and cloud providers. Looks like the current monolithic implementation for cleaning up resources wouldn't be sufficient and its very vast.
Its really filthy for increasing the cleanup scope of in terms of resource types, criterias etc.
Hence I would like to open the discussion with the community to help us decide on a design pattern that uses OOPs concepts for the betterment, and simplicity for developers to expand the horizon of cloudwash.
The Abstract classing / layer would really help to force some design pattern for all the cloud providers, criterias, resource types etc, but opening the floor here to hear from you all !!!!
Beta Was this translation helpful? Give feedback.
All reactions