Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove validation on provider_settings #414

Merged
merged 5 commits into from
Oct 10, 2023
Merged

Remove validation on provider_settings #414

merged 5 commits into from
Oct 10, 2023

Conversation

jradtilbrook
Copy link
Contributor

PR checklist:

  • docs/ updated
  • tests added
  • an example added to examples/ (useful to demo new field/resource)
  • CHANGELOG.md updated with pending release information

@jradtilbrook jradtilbrook requested a review from mcncl October 6, 2023 04:40
mcncl
mcncl previously approved these changes Oct 6, 2023
james2791
james2791 previously approved these changes Oct 6, 2023
@jradtilbrook jradtilbrook dismissed stale reviews from james2791 and mcncl via cf3e849 October 9, 2023 06:53
@jradtilbrook jradtilbrook changed the title Allow filter_condition on bitbucket Remove validation on provider_settings Oct 9, 2023
Copy link
Contributor

@james2791 james2791 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed!

@jradtilbrook jradtilbrook merged commit 9095506 into main Oct 10, 2023
@jradtilbrook jradtilbrook deleted the bugs_1.0.2 branch October 10, 2023 00:01
@scadu
Copy link

scadu commented Oct 10, 2023

Not sure if I missed that discussion, or it's been conducted internally, but why verification is removed shortly after it's been added to the provider? Just wanted to learn a little more.

@jradtilbrook
Copy link
Contributor Author

@scadu we discussed pros/cons internally. It's related to a few issues that were raised after the 1.0 release. Adding the validation was to try to improve the experience and reduce the occurrence of bugs, but after the issues raised and more thought/understanding, we believe the validation was more trouble than it was worth. We may come back to something in the future though, but for now it was the wrong direction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants