-
Notifications
You must be signed in to change notification settings - Fork 16
Add Icinga secrets to beaker job #73
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
base: v3
Are you sure you want to change the base?
Conversation
To access Icinga EL repos, we need basic authentication. Vox Pupuli has test secrets. This relates to voxpupuli/puppet-icingadb#51
There was a problem hiding this 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.
|
https://docs.github.com/en/actions/sharing-automations/reusing-workflows#limitations states:
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. |
I had the same issues. I don't like the current approach, but I wasn't able to find an alternative. |
|
I wonder if we can somehow pass a hash so we don't need to special case it |
|
Linking back from IRC: we have the Perhaps we can implement something more generic in |
To access Icinga EL repos, we need basic authentication. Vox Pupuli has test secrets. This relates to voxpupuli/puppet-icingadb#51