Skip to main content
Skip to content

CustomConnectorForkUpstreamState

Where a published fork stands against its base. It follows its base's runtime content (manifest, handlers/, lib/; a CHANGELOG or README update is not a move) by rebuilding on its next run: CURRENT (the base has not moved), PENDING (it moved, or the base is a fork whose own base moved; the next run builds), FOLLOWED (running a build on the current base), CONFLICTS (running it, with paths both sides changed keeping the fork's content), BUILD_FAILED (the build on the current base failed; the version runs what it was published with). CONFLICTS and BUILD_FAILED also raise a connector.fork_upstream admin alert.

enum CustomConnectorForkUpstreamState {
  BUILD_FAILED
  CONFLICTS
  CURRENT
  FOLLOWED
  PENDING
}

Values​

CustomConnectorForkUpstreamState.BUILD_FAILED​

CustomConnectorForkUpstreamState.CONFLICTS​

CustomConnectorForkUpstreamState.CURRENT​

CustomConnectorForkUpstreamState.FOLLOWED​

CustomConnectorForkUpstreamState.PENDING​

Member Of​

CustomConnectorForkUpstream object