Skip to content

[Code] APM/Code Integration POC#46402

Closed
rylnd wants to merge 8 commits intoelastic:masterfrom
rylnd:apm-repo-map
Closed

[Code] APM/Code Integration POC#46402
rylnd wants to merge 8 commits intoelastic:masterfrom
rylnd:apm-repo-map

Conversation

@rylnd
Copy link
Contributor

@rylnd rylnd commented Sep 23, 2019

Summary

This is a basic proof of concept for elastic/code#1637. It is meant to be a general-purpose component for integrations with Code. It performs the following duties:

  • Links to a repo/file in the code app given some contextual props (currently: a stack frame)
  • Allows one to select from a list of repos and trigger a callback once selected
  • Allows one to import a new repo to Code, and trigger a callback once the import call is complete.

Data and actions are both stubbed.

Questions this has surfaced:

  • How will APM fetch/store Code repo information (naive would be N+1 if CodeIntegration component did it)
  • Does APM have need for a callback to notify of an import's success? If so, how will that work?
  • Is the Project URI (e.g. https://github.com/rylnd/dotfiles) sufficient for the Code side of the Code/Service mapping in APM?

@elasticmachine
Copy link
Contributor

Pinging @elastic/code

@elasticmachine
Copy link
Contributor

💔 Build Failed

@mw-ding
Copy link
Contributor

mw-ding commented Sep 25, 2019

A couple of follow up steps per offline discussion:

  • having a flag to protect the temporary showcase page
  • formalize the service mapping component to check in this PR

Regarding questions:

How will APM fetch/store Code repo information (naive would be N+1 if CodeIntegration component did it)

I would suggest keep it simple first and add it later in case we need them.

Does APM have the need for a callback to notify of an import's success? If so, how will that work?

At least for the first iteration, this is not necessary. We can add it if it's required next.

Is the Project URI (e.g. https://github.com/rylnd/dotfiles) sufficient for the Code side of the Code/Service mapping in APM?

yes

I want to build this off of a general RepoSelector component, that
allows one to select or import a new repo to Code. When selected, a
callback is invoked with some Code-specific arguments.
Since the value will not have changed on blur, onChange has exactly the
same effect, here.
We're going to need this on both the projects page and now the
RepoSelectorComponent.
* All the actions are stubbed
* It needs style
* There are questions about data sources and persistence
Adds copy and some basic CSS.
There's still a gap here because this is Code's data, not APM's data,
but this is a little closer to what we'll have in the end.
onImportSuccess will be invoked with the imported repo's URI when the
import has succeeded. That's the idea, at least.
@elasticmachine
Copy link
Contributor

💔 Build Failed

@rylnd rylnd mentioned this pull request Oct 2, 2019
7 tasks
@rylnd
Copy link
Contributor Author

rylnd commented Oct 3, 2019

Closing in favor of #47180

@rylnd rylnd closed this Oct 3, 2019
@rylnd rylnd deleted the apm-repo-map branch October 3, 2019 00:02
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.

3 participants