ci: drop the application scaffolding workflow - #12
Merged
Merged
Conversation
ci.yml treats this repository as a nullplatform application: np build start, docker build -t main ., np asset push. That made sense while the root Dockerfile was the http-echo placeholder, and it is what scaffolded repositories get. It is not what a service repository does. #9 replaced the placeholder with Dockerfile.aurora-postgres-{server,db}, so 'docker build .' now fails with 'failed to read dockerfile: open Dockerfile: no such file or directory' on every push to main. The images this repository actually publishes are built by release.yml. services-postgresql-rds, services-s-3 and services-dynamo-db carry no equivalent workflow.
gdrojas
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
ci.yml(ci-nullplatform) treats this repository as a nullplatform application:That is the workflow a scaffolded application repository gets. It worked while the root
Dockerfilewas thehttp-echoplaceholder, because there was something to build.#9 replaced that placeholder with
Dockerfile.aurora-postgres-serverandDockerfile.aurora-postgres-db, so every push to main now fails:Why removing rather than fixing
A service repository does not publish itself as an application asset. The images it ships are the two worker images, and those are built and registered by
release.yml.services-postgresql-rds,services-s-3andservices-dynamo-dbcarry no equivalent workflow — this one is scaffolding that outlived its Dockerfile.