feat: add generic BuildArgs for BuildpackArtifact

[bogdannazarenko]

Fixes: #9744
Related: N/A
Merge before/after: N/A

Description

Adding generic BuildArgs []string field on BuildpackArtifact. This allows users to pass any additional args to pack build (e.g. --network, --cache-image) without requiring future schema changes.

Example problem: GCP CloudBuild application default credentials are only available on docker network "cloudbuild," hence we need to specify that network for build pack to access that network for proper workload identity authentication for access to things such as Artifact Registries.

User facing changes (remove if N/A)

Addition property available to set on buildpack image build configurations.

[bogdannazarenko]

@Darien-Lin @katiexzhang @menahyouyeah I generate a new schema version and added by schema changes for the buildpack build Network property. Could one you you please check and trigger further tests? Thank you

[menahyouyeah]

Would it be possible to split this into 2 commits - one with all the schema related changes and another with the logic changes to make it easier to review?

[menahyouyeah]

Instead of adding just the Network arg can you do something similar to #9696. Basically a BuildArgs []string or something along those lines so that in the future if people wanted to pass additional args there wouldn't need to be any additional logic or schema change.

[bogdannazarenko]

@menahyouyeah I implemented your suggestion with general BuildArgs property. Please re-review when you get a second

[bogdannazarenko]

@Darien-Lin @katiexzhang @menahyouyeah could you please re-review when you get a chance? Thank you

[Darien-Lin]

Generally the maintainers of this Github is responsible for bumping up schema changes as there is a process to follow. Can you revert the schema changes and just have the new flags?

[bogdannazarenko]

@Darien-Lin I removed schema changes. Thank you

[bogdannazarenko]

Generally the maintainers of this Github is responsible for bumping up schema changes as there is a process to follow. Can you revert the schema changes and just have the new flags?

@Darien-Lin just fyi, the DEVELOPMENT.md instructs to generate a new schema version and commit. I'm unable to build the binary if I don't generate the schema.

➜ make          
GOOS=darwin GOARCH=arm64 CGO_ENABLED=1 \
            go build -mod="vendor" -gcflags="all=-N -l" -tags "timetzdata release " -ldflags "-X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.version=v2.14.0-56-gfc3e3263e -X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.buildDate=2026-04-22T11:18:36Z -X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.gitCommit=fc3e3263e34a617bf5336915b1550355e5c19e2d -s -w " -o out/skaffold github.com/GoogleContainerTools/skaffold/v2/cmd/skaffold
# github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/build/gcb
pkg/skaffold/build/gcb/buildpacks.go:51:31: artifact.BuildArgs undefined (type *"github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/schema/latest".BuildpackArtifact has no field or method BuildArgs)
make: *** [out/skaffold] Error 1

Are those docs intended for Maintainers? Should I update with a note that it's for maintainer only?

[Darien-Lin]

Generally the maintainers of this Github is responsible for bumping up schema changes as there is a process to follow. Can you revert the schema changes and just have the new flags?

@Darien-Lin just fyi, the DEVELOPMENT.md instructs to generate a new schema version and commit. I'm unable to build the binary if I don't generate the schema.

➜ make          
GOOS=darwin GOARCH=arm64 CGO_ENABLED=1 \
            go build -mod="vendor" -gcflags="all=-N -l" -tags "timetzdata release " -ldflags "-X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.version=v2.14.0-56-gfc3e3263e -X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.buildDate=2026-04-22T11:18:36Z -X github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/version.gitCommit=fc3e3263e34a617bf5336915b1550355e5c19e2d -s -w " -o out/skaffold github.com/GoogleContainerTools/skaffold/v2/cmd/skaffold
# github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/build/gcb
pkg/skaffold/build/gcb/buildpacks.go:51:31: artifact.BuildArgs undefined (type *"github.com/GoogleContainerTools/skaffold/v2/pkg/skaffold/schema/latest".BuildpackArtifact has no field or method BuildArgs)
make: *** [out/skaffold] Error 1

Are those docs intended for Maintainers? Should I update with a note that it's for maintainer only?

I am attempting to make the cut here: #10059
From what I can tell, in the past, we've allowed developers to submit the code changes with the config update, but since there's quite a bit of diffs now, we've generally had maintainers do it. I think the doc should be updated.

[Darien-Lin]

I have made the cut, so feel free to rebase and add the new fields

[Darien-Lin]

The config struct needs to be updated to have these new fields

[bogdannazarenko]

The config struct needs to be updated to have these new fields

yep, thank you @Darien-Lin. I rebased and updated the structure.

[bogdannazarenko]

@Darien-Lin looks like the same failed integrations tests as from the other PRs.
https://github.com/GoogleContainerTools/skaffold/actions/runs/24799437758/job/72582753938?pr=9745#step:19:3550

[bogdannazarenko]

@Darien-Lin thanks for your help