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

Verify sync-release on stage on MP+ #2130

Closed
2 of 3 tasks
mfocko opened this issue Jul 27, 2023 · 1 comment
Closed
2 of 3 tasks

Verify sync-release on stage on MP+ #2130

mfocko opened this issue Jul 27, 2023 · 1 comment
Assignees
@lbarcziova
Labels
area/fedora Related to Fedora ecosystem area/general Related to whole service, not a specific part/integration. 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/high This issue impacts multiple/lot of users.

Comments

@mfocko
Copy link
Member

mfocko commented Jul 27, 2023 •
edited by lbarcziova
Loading

After the migration to the MP+ we need to be explicit about the firewall rules. We have already hit an issue with the TF API that's been fixed already.

sync-release is mostly affected by this, since it allows user actions and downloads source archives from hostings, such as crates.io or PyPI

TODO:

  • Extend the staging allowlist with the namespaces from prod (to allow painless bootstrap)
  • Make a blog post and urge users to try enabling stage and enable rawhide or latest Fedora release to run propose-downstream or pull-from-upstream on staging too
    It's just one more PR and it should catch the firewall issues. (Create post to encourage testing staging release sync packit.dev#724)
  • (optionally) go through the recent sync releases and configs to see if there are any good candidates1 for trying it out on stage

Footnotes

  1. What to consider a good candidate

    • different archive hosting
      we will definitely test the PyPI, so I'd look out for any other package managers provided by languages, e.g. Cargo (crates.io hosting) for Rust, Go, Gems for Ruby, npm for JS/TS
    • actions
      though I am definitely against allowing fetching scripts/specs/etc. from self-hosted destinations
    ↩
@lachmanfrantisek lachmanfrantisek added area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. area/general Related to whole service, not a specific part/integration. gain/high This brings a lot of value to (not strictly a lot of) users. labels Jul 27, 2023
@mfocko mfocko mentioned this issue Aug 21, 2023
Closed
2 tasks
@lbarcziova lbarcziova self-assigned this Aug 29, 2023
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Aug 30, 2023
@lbarcziova
Create post to encourage testing staging release sync
eb891e4 
Related to packit/packit-service#2130
@lbarcziova lbarcziova mentioned this issue Aug 30, 2023
Merged
3 tasks
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 4, 2023
@lbarcziova
Create post to encourage testing staging release sync
188b0da 
Related to packit/packit-service#2130
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 4, 2023
@lbarcziova
Create post to encourage testing staging release sync
084675b 
Related to packit/packit-service#2130
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 4, 2023
@lbarcziova
Create post to encourage testing staging release sync
28d7ded 
Related to packit/packit-service#2130
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 5, 2023
@lbarcziova
Create post to encourage testing staging release sync
742015a 
Related to packit/packit-service#2130
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 5, 2023
@lbarcziova
Create post to encourage testing staging release sync
2bb81b6 
Related to packit/packit-service#2130
lbarcziova added a commit to lbarcziova/packit.dev that referenced this issue Sep 5, 2023
@lbarcziova
Create post to encourage testing staging release sync
81a1c2a 
Related to packit/packit-service#2130
softwarefactory-project-zuul bot added a commit to packit/packit.dev that referenced this issue Sep 5, 2023
@softwarefactory-project-zuul
Create post to encourage testing staging release sync (#724)
10543dc 
Create post to encourage testing staging release sync

Related to packit/packit-service#2130
Ideas where to share (feel free to add):

 Mastodon
 pinned issue in GitHub
 in the markdown body in Github checks

Reviewed-by: Matej Focko
Reviewed-by: František Lachman <[email protected]>
Reviewed-by: Laura Barcziová
@lbarcziova
Copy link
Member

We have decided to create a separate card for scraping the configs and trying out the potential problematic actions, therefore closing this as done.

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

@lbarcziova lbarcziova

Labels
area/fedora Related to Fedora ecosystem area/general Related to whole service, not a specific part/integration. 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/high This issue impacts multiple/lot of users.
Projects
Packit Kanban Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mfocko @lachmanfrantisek @lbarcziova