@scshitole Stop pushing to master about terraform-provider-bigip HOT 3 CLOSED

@fcgravalos agreed this was exception as customer wanted the fix, but now connivence them to use pool attachment resource, hence forth will have commits in dev branch and PR after that.

from terraform-provider-bigip.

@scshitole I understand your rush, but you opened the provider to an opensource community so there's no single customer. This is not your customer's product, this is an opensource project. If a customer require specific customizations that are not aligned with the project, I'd recommend you to fork the repo.

from terraform-provider-bigip.

Thank you @scshitole!

Just bear in mind that specific customer/user need cannot dictate direct changes like that to a community driven project, changes here impact a wide range of users and should be properly reviewed and tested.

Any one user that wants something changed can file a change request (issue) and/or submit a PR, if that change is accepted - great, if not - he may always fork the project and make any changes he deems necessary for his specific needs.

This is a common practice when working with any OSS tool.

from terraform-provider-bigip.