teamhephy/builder

Allow namespacing of private registry images

Open

#41 opened on Jul 17, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (12 forks)auto 404
Hacktoberfestenhancementgood first issue

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

Right now, if the ECR registry is namespaces in the values.yml is like this:

    registryid: "373147738271"
    hostname: "373147738271.dkr.ecr.us-east-1.amazonaws.com/team_hephy"

The deis-builder still creates image repo in ECR without the namespace.

Error:

Successfully built 2641d630d4e2
Pushing to registry
name unknown: The repository with name 'team_hephy/slack' does not exist in the registry with id '318742728771'
remote: 2018/07/17 16:15:49 Error running git receive hook [Build pod exited with code 1, stopping build.]

The deis-builder will not be able to push because it has not idea of namespacing the images right now. This needs to be fixed in the code.

Contributor guide

Research direction
Examine how the builder resolves the image repository path from the registry configuration and ensure the namespace (e.g., 'team hephy/') is included when pushing to ECR.
Tech stack
go
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70