Extensions: Support token access for remote repositories #121886
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#121886
Loading…
Reference in New Issue
No description provided.
Delete Branch "ideasman42:pr-extensions-acess-token"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This introduce a new "secret" per-repository property of type password.
This only shows for remote repositories, and it doesn't show for the "https://extensions.blender.org" repository.
Ref: #121856
TODOs:
Add Remote Repository dialog:
Extension settings:
Extension settings expanded:
ea5e22b268
todd7046c87b
Updated:
The remaining changes are are to implement this as part of HTTP requests.
Not sure if it should be advanced, this seems like a pretty common field for repositories. @fsiddi thoughts?
[edit: let me test it actually, before commenting on it :) ]
Some screenshots from the patch as it is now. The secret only shows when the Use Access Token is on:
I can see the reasoning. Not sure what I think, I'm probably fine
The text field it self is not in advanced, when adding the repository you can enable access-token, that controls the field being displayed. If you wish to change this (as in, access a repository with an access-token which previously didn't need one - or the reverse) after creating the repository, it can be done in advanced because this is a fairly special-case.
This was done because I expect many/most repositories won't use an access token, showing it there for all repositories because they *could* seems odd to me, especially when leaving it empty makes it seem like some necessary field has been left out.
I'd make sure that the field is easily discoverable, especially when adding a repo. Otherwise most instructions will say "click on the advanced settings", which I rather avoid.
Given that this is prominent when adding a repo I think it is ok. Even if you have to update the token the repo will have it visible since you set it as use token once.
Patch updated with the latest UI changes from https://devtalk.blender.org/t/2024-05-21-extensions-project/34751#design-topics-4
7f4d989c34
toab1ab49b3b
95bf6bf09a
to67fd339fee
Committed
08df46d7cd
.WIP: Extensions: Support token access for remote repositoriesto Extensions: Support token access for remote repositoriesPull request closed