Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for passing build args to signers #275

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

cpuguy83
Copy link
Member

@cpuguy83 cpuguy83 commented May 29, 2024

I considered extending this to allow this for any kind of frontend (and as such sticking it into the dalec.Frontend type), however there really shouldn't be different vars passed to target frontends. Hence why I am restricting this to just signers for now.

If we decide to later we can add this more generically, however it will be much more difficult to take it away if we decide it was a bad idea.

Related to #263

@cpuguy83 cpuguy83 requested a review from a team as a code owner May 29, 2024 23:57
Copy link
Contributor

@pmengelbert pmengelbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Just to make sure I understand how dalec will behave after this PR is merged, is the following accurate?

  1. Values needed for the signing image can be provided via the package_config section, either on the spec level, or on the level of a specific target. (good for packages with both linux + windows targets).
  2. These values can be supplied at build-invocation time by leveraging the spec's args.
  3. The args will be read by the consumer (i.e. the signing image) via the filesystem, and will have to be initialized into the environment on that end.

The only actionable request I have is that this should be captured in an example somewhere (in the docs/examples directory perhaps). As we keep adding features like this, having an up-to-date example with the kitchen sink makes it easier for all the developers on the project to track spec and feature changes.

@cpuguy83
Copy link
Member Author

cpuguy83 commented Jun 3, 2024

Updated with doc updates.

@pmengelbert
Copy link
Contributor

I think this needs to be rebased, then it should pass the CI

Copy link
Contributor

@pmengelbert pmengelbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, will wait for rebase + CI passage to approve.

I considered extending this to allow this for any kind of frontend (and
as such sticking it into the `dalec.Frontend` type), however there
really shouldn't be different vars passed to target frontends.
Hence why I am restricting this to just signers for now.

If we decide to later we can add this more generically, however it will
be much more difficult to take it away if we decide it was a bad idea.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
@cpuguy83
Copy link
Member Author

This was rebased, FYI.

@cpuguy83 cpuguy83 enabled auto-merge (rebase) June 18, 2024 20:28
Copy link
Contributor

@pmengelbert pmengelbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@cpuguy83 cpuguy83 merged commit 0bb8ba7 into Azure:main Jun 20, 2024
10 checks passed
@cpuguy83 cpuguy83 deleted the signer_args branch June 20, 2024 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants