Skip to content

Edge case: registry context path differs from transfer repository #102

@gczuczy

Description

@gczuczy

Description

In same rare cases it happens that for the product transfer a repository subpath is being used within the target registry, and the repository context provided for the product installation is on the root.

Example:

  • Product was transferred to 42069.ecr.amazonaws.com/kyma/foobar
  • The registry context provided has a baseUrl only for the root:
    baseUrl: 42069.ecr.amazonaws.com

KLM has already implemented this: kyma-project/lifecycle-manager#3130

Reasons

Sometimes restricted market operators do this.

Attachments

None.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions