You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by la...@apache.org on 2026/07/06 04:37:28 UTC

(airavata-custos) branch privilege-enforcement updated (b19c91120 -> 417825a57)

This is an automated email from the ASF dual-hosted git repository.

lahirujayathilake pushed a change to branch privilege-enforcement
in repository https://gitbox.apache.org/repos/asf/airavata-custos.git


    omit b19c91120 Introduce privilege keys for all resources and enforce them on every route
    omit 7bde73fdd Split server handlers into per-resource files
    omit ba77028f3 Updated the privilege catalog and changed the architecture and connector guide to align with that
    omit 8ea636853 Add Flask dependency for AMIE mock server
    omit eee3b41ad Add instructions for loading sample data and refine AMIE setup docs
    omit d3a8951e9 Regenerate portal SDK and remap ability rules for the new privilege keys
    omit 6b65269f2 Extend privileges and user statuses in the API and models
    omit a4edb8ce3 Updated the INSTALL.md
    omit 46b7d61b7 dropped the access_ci db
    omit 481ed580d Updated env examples and remove outdated super_admin privilege seed
    omit 0b27eb2c6 Expand super_admin role to include all registered privileges
    omit 280750270 Temporarily bypass `email_verified` gate due to COmanage issue
    omit 8049aaf91 Considered the PENDING status for merging
    omit 40481d410 Update tests and baseline data to reflect `PENDING` status for users
    omit c26e5faa5 Bootstrap admin user and link upstream-provisioned users on first OIDC sign-in
     add 6b795aa04 Bootstrap admin user and link upstream-provisioned users on first OID… (#512)
     add ab17e58f3 Bump golang.org/x/net in /extensions/SSH-Certificate-Signer (#515)
     add cdde4c491 Split server handlers into per-resource files (#513)
     add 417825a57 Introduce privilege keys for all resources and enforce them on every route

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (b19c91120)
            \
             N -- N -- N   refs/heads/privilege-enforcement (417825a57)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 extensions/SSH-Certificate-Signer/go.mod |  8 ++++----
 extensions/SSH-Certificate-Signer/go.sum | 20 ++++++++++----------
 2 files changed, 14 insertions(+), 14 deletions(-)