Skip to content

Conversation

@sahil143
Copy link
Contributor

ODC-story: https://issues.redhat.com/browse/ODC-2461

This Pr adds the traffic connector and is based on the mock data. To test this PR locally run below cmds and select the bookinfo namespace

oc new-project bookinfo
oc apply -n bookinfo -f https://raw.githubusercontent.com/Maistra/bookinfo/maistra-1.0/bookinfo.yaml

Screenshot from 2020-01-21 18-07-34

@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. component/dev-console Related to dev-console labels Jan 21, 2020
@andrewballantyne
Copy link
Contributor

/kind feature

cc @openshift/team-devconsole-ux

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 21, 2020
Copy link
Contributor

Choose a reason for hiding this comment

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

So consts for other connectors doesnt have an edge suffix, for consistency either add edge suffix in all connectors or remove it from this one.

Copy link
Contributor

Choose a reason for hiding this comment

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

Why not use the traffic data type here?

Copy link
Contributor

Choose a reason for hiding this comment

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

Can we use types instead of any?

@sahil143 sahil143 force-pushed the connector-traffic branch 2 times, most recently from e4ed0ab to 432ed1b Compare January 23, 2020 04:08
@divyanshiGupta
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2020
@divyanshiGupta
Copy link
Contributor

For now I think it is okay to use the mock data and later when we have the kiali api refactor the code to use it. cc: @christianvogt

Copy link
Contributor

@andrewballantyne andrewballantyne left a comment

Choose a reason for hiding this comment

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

Looks good, needs tests. @sahil143 please log a task in JIRA, assign it to yourself, and put it in the next sprint (179). You'll need to write tests next week.

@andrewballantyne
Copy link
Contributor

andrewballantyne commented Jan 24, 2020

Not sure how to test the connector part yet; will look to follow https://issues.redhat.com/browse/ODC-2505 shortly.

@andrewballantyne
Copy link
Contributor

UX note... this looks weird and not like a dashed line. Is this going to be confusing to the user?

cc @openshift/team-devconsole-ux

Screen Shot 2020-01-24 at 10 29 52 AM
Screen Shot 2020-01-24 at 10 30 03 AM

Dashed lines don't overlap all that well.

Copy link
Contributor

@andrewballantyne andrewballantyne left a comment

Choose a reason for hiding this comment

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

This looks good to me minus the overlapping connectors. We'll have to make sure we show this to UX and get feedback...

I'm approving this PR because it looks good to me and is a blocker for @divyanshiGupta 's PR.

@sahil143 Please log that Unit Test ticket when JIRA comes back up.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 24, 2020
@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 24, 2020
Copy link
Contributor

@andrewballantyne andrewballantyne left a comment

Choose a reason for hiding this comment

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

Some changes needed. You can log a ticket and address these later; nothing is critical.

A new test, and a use of a constant over a magic string.

Copy link
Contributor

Choose a reason for hiding this comment

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

You modified the output here and it didn't fail a test 😕 I think we need to write a test for this condition too.. otherwise we'll not catch a break if this violates the status quo.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Even if this condition is not true it doesn't affect the edges array. it's just that Traffic connector will be not be added to the edges array.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, doh - right it wouldn't fail pre-existing tests. My brain is half functioning today 😆 But we still need to write a test for if it is truthy.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes I did for falsy

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm confused by this comment:

yes I did for falsy

This didn't exist during my last test, did it? I'm 99% I didn't see the falsy test lol.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, there wasn't any test to check the condition. But now I added for both falsy and truthy. 😉

Copy link
Contributor

Choose a reason for hiding this comment

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

I believe there is a type for this (I didn't know this when previously reviewing)...

Suggested change
nodes.filter(({ data }) => data.nodeType === 'workload');
nodes.filter(({ data }) => data.nodeType === TYPE_WORKLOAD);

From frontend/packages/dev-console/src/components/topology/const.ts

@openshift-ci-robot openshift-ci-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 24, 2020
@sahil143 sahil143 force-pushed the connector-traffic branch 2 times, most recently from 9bfdbcc to 1ee1752 Compare January 24, 2020 16:32
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, divyanshiGupta, karthikjeeyar, sahil143

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

The pull request process is described here

Details 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-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

25 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@sahil143
Copy link
Contributor Author

Commit from this PR is already merged in master through PR #4026. Closing this.

@sahil143 sahil143 closed this Jan 27, 2020
@andrewballantyne
Copy link
Contributor

e2e tests were just not passing here... so we took a two prong approach and it worked out 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. component/dev-console Related to dev-console kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants