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.

Sign up for GitHub

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

Jump to bottom

[Move Openshift tests to Testing Farm] Enable secrets #564

Open
5 tasks
majamassarini opened this issue Apr 18, 2024 · 0 comments
Open
5 tasks

[Move Openshift tests to Testing Farm] Enable secrets #564

majamassarini opened this issue Apr 18, 2024 · 0 comments
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@majamassarini
Copy link
Member

majamassarini commented Apr 18, 2024 •
edited
Loading

OpenShift Local pull secret and packit-service secrets have to be encrypted in the Testing Farm bare metal instance.

  • Write the ansible code to generate encrypted secrets

  • Choose one of the following way to pass decryption key:

    • If this code is already available in production (it should be after DevConf) use it.

    Otherwise

    • Ask Testing Farm team to use Testing Farm Github action until the above is available
    • Configure the above as soon as it is enabled.
@majamassarini majamassarini mentioned this issue Apr 18, 2024
Open
6 tasks
@majamassarini majamassarini added area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Apr 18, 2024
@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Apr 22, 2024
@majamassarini majamassarini mentioned this issue Sep 5, 2024
Merged
softwarefactory-project-zuul bot added a commit that referenced this issue Sep 16, 2024
@softwarefactory-project-zuul
Test deployment locally with tmt (from packit branch) (#581)
d29ce15 
Test deployment locally with tmt (from packit branch)

To be able to access secrets and test ansible scripts using github secrets in the testing farm github action I need to create a PR from the packit repo itself (and not from a fork).
This is the reason why the PR is duplicated at the moment.
Should fix #562 #563 #564 #565

Reviewed-by: Laura Barcziová
Reviewed-by: Matej Focko
Reviewed-by: Maja Massarini
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: priority-backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@majamassarini