Skip to content

Conversation

@bastelfreak
Copy link
Member

@bastelfreak bastelfreak commented Apr 14, 2025

To access Icinga EL repos, we need basic authentication. Vox Pupuli has test secrets. This relates to voxpupuli/puppet-icingadb#51

@bastelfreak bastelfreak added the enhancement New feature or request label Apr 14, 2025
@bastelfreak bastelfreak self-assigned this Apr 14, 2025
To access Icinga EL repos, we need basic authentication. Vox Pupuli has
test secrets. This relates to voxpupuli/puppet-icingadb#51
Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

I'd like to avoid this if possible. Can't we set the env vars in the job itself?

Edit: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#defining-environment-variables-for-a-single-workflow documents how to set them at the top level. I'd expect that to work. We'll just need to fiddle with modulesync to make it possible.

@ekohl
Copy link
Member

ekohl commented Apr 14, 2025

https://docs.github.com/en/actions/sharing-automations/reusing-workflows#limitations states:

Any environment variables set in an env context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information, see Store information in variables and Accessing contextual information about workflow runs.

So that's pretty limiting. However, I still think we shouldn't introduce repo specific changes into gha-puppet. At this point I struggle to figure out how.

@bastelfreak
Copy link
Member Author

At this point I struggle to figure out how.

I had the same issues. I don't like the current approach, but I wasn't able to find an alternative.

@ekohl
Copy link
Member

ekohl commented Apr 14, 2025

I wonder if we can somehow pass a hash so we don't need to special case it

@ekohl
Copy link
Member

ekohl commented Apr 16, 2025

Linking back from IRC: we have the BEAKER_FACTER_* env vars. Those would be good to support.

Perhaps we can implement something more generic in metadata2gha to expose more env vars into Beaker, similar to --beaker-facter but something that doesn't end up in the testing matrix name etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants