Skip to content
This repository was archived by the owner on Jun 26, 2024. It is now read-only.

Conversation

baijum
Copy link
Contributor

@baijum baijum commented Aug 4, 2021

A name and selector MUST NOT be defined in the same application
reference

Fix #974

@codecov
Copy link

codecov bot commented Aug 4, 2021

Codecov Report

Merging #1005 (2a4617b) into master (bc69c60) will increase coverage by 0.04%.
The diff coverage is 100.00%.

❗ Current head 2a4617b differs from pull request most recent head ca15119. Consider uploading reports for the commit ca15119 to get more accurate results
Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1005      +/-   ##
==========================================
+ Coverage   58.03%   58.08%   +0.04%     
==========================================
  Files          29       29              
  Lines        1642     1646       +4     
==========================================
+ Hits          953      956       +3     
  Misses        563      563              
- Partials      126      127       +1     
Impacted Files Coverage Δ
apis/binding/v1alpha1/servicebinding_webhook.go 63.15% <100.00%> (+21.49%) ⬆️
apis/spec/v1alpha3/servicebinding_webhook.go 63.15% <100.00%> (+21.49%) ⬆️
...kg/reconcile/pipeline/context/spec_binding_impl.go 72.54% <100.00%> (ø)
pkg/binding/model.go 87.50% <0.00%> (-2.70%) ⬇️
pkg/binding/definition.go 47.54% <0.00%> (-2.46%) ⬇️
pkg/binding/annotationmapper.go 87.34% <0.00%> (-0.16%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bc69c60...ca15119. Read the comment docs.

@baijum baijum requested a review from pedjak August 31, 2021 11:43
Copy link
Contributor

@pedjak pedjak left a comment

Choose a reason for hiding this comment

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

we should not even allow creating service binding instances that have name and selector defined.

Validation webhooks are our friend here - the check should be implemented there instead.

@baijum
Copy link
Contributor Author

baijum commented Sep 11, 2021

we should not even allow creating service binding instances that have name and selector defined.

Validation webhooks are our friend here - the check should be implemented there instead.

Done.

@pedjak pedjak removed the request for review from pratikjagrut September 12, 2021 09:09
Copy link
Contributor

@pedjak pedjak left a comment

Choose a reason for hiding this comment

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

the checks must exists for both APIs and acceptance tests should verify if they are active.

@baijum baijum force-pushed the name-selector branch 3 times, most recently from 8bd5b5c to 4e61c4a Compare September 14, 2021 11:06
@baijum baijum force-pushed the name-selector branch 3 times, most recently from 752e2e9 to 2d52808 Compare September 21, 2021 11:40
@baijum baijum force-pushed the name-selector branch 2 times, most recently from f17848c to 3bf4079 Compare October 5, 2021 06:08
@@ -4,6 +4,7 @@ import (
"context"
"encoding/base64"
e "errors"

Copy link
Contributor

Choose a reason for hiding this comment

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

nit: whitespace change, please revert.

"""

@negative
Scenario: Cannot create Service Binding with name and label selector in the spec API
Copy link
Contributor

Choose a reason for hiding this comment

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

annotation this scenario with @spec tag.

Copy link
Contributor

@pedjak pedjak left a comment

Choose a reason for hiding this comment

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

/lgtm

please squash commits

A name and selector MUST NOT be defined in the same application
reference

Use webhook to validate

Fix redhat-developer#974

Signed-off-by: Baiju Muthukadan <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm label Oct 6, 2021
@baijum
Copy link
Contributor Author

baijum commented Oct 6, 2021

please squash commits

Done

@pedjak
Copy link
Contributor

pedjak commented Oct 6, 2021

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm label Oct 6, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pedjak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Oct 6, 2021
@baijum
Copy link
Contributor Author

baijum commented Oct 6, 2021

/test 4.7-acceptance

@openshift-merge-robot openshift-merge-robot merged commit 254625f into redhat-developer:master Oct 6, 2021
@baijum baijum deleted the name-selector branch October 7, 2021 06:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A name and selector MUST NOT be defined in the same application reference
3 participants