What should be installed by default with porter? #1192
Labels
2 - 🍕
Pizza should be eaten daily
breaking change 💥
Breaking changes to Porter's CLI, config or behavior
Milestone
To assist with discoverability before with had the package index, we opted to install pretty much everything by default. Now that we have more mixins and some are either more stable, updated more often, and are cloud specific, I think it would be helpful to come up with guidelines for which mixins and plugins should be installed by default and which we should encourage people to use porter to install separately.
Reasons to limit what is installed by default:
The only mixin that must be installed by default is the exec mixin. I would say that the mixins that we should stop installing by default are any cloud provider mixins (glcoud, aws, azure/az/arm). Anything that is installed by default will need to have a commitment to being maintained at the highest level of stability and stay up-to-date with each porter release similar to how exec does today.
After that the main question is are there any mixins or plugins that are so integral (like the exec mixin) that we believe that they should be installed by default vs installed at the discretion of the user? After looking over the list of current mixins/plugins I am inclined to say that they all can be installed as needed by the user.
🚨 We really need #975 to do this properly
The text was updated successfully, but these errors were encountered: