All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Orling <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [layerindex-web][PATCH 0/7] Fixes; add Update Layer button; expose branch mapping
Date: Fri, 29 Dec 2023 20:57:07 -0800	[thread overview]
Message-ID: <cover.1703911977.git.tim.orling@konsulko.com> (raw)

This series is the combination of several changes that are best done as
a group because that is how they were developed and more importantly tested.

* Update requirements.txt to the "latest" versions
* Fix an annoyance in the docker/settings.py which caused the RABBIT_BROKER
  variable to be unparseable, since no default values where set and the
  environment variables do not always exist in the running container context
  (such as running updates)
* Enable production (trusted by browser) cert creation by dockersetup.py via
  Let's Encrypt. This should help publicly facing instances avoid unnecessary
  churn of the staging certs.
* Fix a typo that broke Branch Comparison
  [YOCTO #15332]
* Expose the "actual_branch" branch mapping in the web UI (previously
  only available in the admin interface.
  [YOCTO #8008]
* Add the ability to trigger a layer update from the web UI (is_staff users
  only).
  [YOCTO #12484]
* Improve the handling of actual_branch by the update.py script (and friends)
  to allow scripted creation/updates of stable branches with actual_branch set.
  This should enable better utilization of LAYERSERIES_COMPAT in the future.

The following changes since commit 4712f00df73f86ab557cf499b6b20aac3f738535:

  utils.py: fix unclosed ( (2023-11-22 11:06:10 -0800)

are available in the Git repository at:

  https://github.com/moto-timo/layerindex-web timo/update-button-actual-branch
  https://github.com/moto-timo/layerindex-web/tree/timo/update-button-actual-branch

Tim Orling (7):
  requirements.txt: bump all to latest
  layerindex/views.py: fix parse_view typo
  docker/settings.py: fix RABBIT_BROKER TypeError
  dockersetup.py: enable production Let's Encrypt
  layerindex: Add actual_branch to forms and views
  layerindex: add Update Layer UI feature
  layerindex: improve updates for actual_branch

 docker/settings.py                     |   2 +-
 dockersetup.py                         |   9 +-
 layerindex/forms.py                    |  15 ++++
 layerindex/update.py                   |  39 +++++---
 layerindex/update_layer.py             |   8 ++
 layerindex/urls.py                     |   2 +-
 layerindex/urls_branch.py              |   3 +-
 layerindex/utils.py                    |   7 +-
 layerindex/views.py                    |  42 ++++++++-
 requirements.txt                       |  40 ++++-----
 templates/layerindex/detail.html       |   3 +
 templates/layerindex/reviewdetail.html |   3 +
 templates/layerindex/updatelayer.html  | 119 +++++++++++++++++++++++++
 13 files changed, 252 insertions(+), 40 deletions(-)
 create mode 100644 templates/layerindex/updatelayer.html

-- 
2.34.1



             reply	other threads:[~2023-12-30  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  4:57 Tim Orling [this message]
2023-12-30  4:57 ` [layerindex-web][PATCH 1/7] requirements.txt: bump all to latest Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 2/7] layerindex/views.py: fix parse_view typo Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 3/7] docker/settings.py: fix RABBIT_BROKER TypeError Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 4/7] dockersetup.py: enable production Let's Encrypt Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 5/7] layerindex: Add actual_branch to forms and views Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 6/7] layerindex: add Update Layer UI feature Tim Orling
2023-12-30  4:57 ` [layerindex-web][PATCH 7/7] layerindex: improve updates for actual_branch Tim Orling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1703911977.git.tim.orling@konsulko.com \
    --to=ticotimo@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.