Page MenuHomePhabricator

Expose Drydock authorizations via Conduit
ClosedPublic

Authored by yelirekim on Sep 24 2016, 6:49 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 3:44 PM
Unknown Object (File)
Fri, Dec 20, 6:54 PM
Unknown Object (File)
Fri, Dec 13, 6:01 PM
Unknown Object (File)
Thu, Dec 12, 5:48 PM
Unknown Object (File)
Thu, Dec 5, 12:31 AM
Unknown Object (File)
Wed, Dec 4, 5:37 AM
Unknown Object (File)
Sun, Dec 1, 8:24 AM
Unknown Object (File)
Nov 4 2024, 3:57 AM
Subscribers

Details

Summary

DrydockAuthorizationSearchEngine was being used solely to display authorizations for a specific blueprint from the web UI and consequently expected that callers set a specific blueprint before performing a query. Here we check to see if a blueprint has been set in cases where the engine could be operating from either Conduit or the web.

Ref T11694

Test Plan
  • called the API method from the console
  • approved an authorization
  • followed the "view all" link from a blueprint page

Diff Detail

Repository
rP Phabricator
Branch
authorization_search (branched from master)
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 13832
Build 17881: Run Core Tests
Build 17880: arc lint + arc unit

Event Timeline

yelirekim retitled this revision from to Expose Drydock authorizations via Conduit.
yelirekim updated this object.
yelirekim edited the test plan for this revision. (Show Details)
epriestley added a reviewer: epriestley.
epriestley added inline comments.
src/applications/drydock/query/DrydockAuthorizationSearchEngine.php
59

Unnecessary? What problem does it create if you omit this?

64

Maybe we should think about picking a better name for an authorization's "Object" now that it's becoming more user-facing, but "authorizee" or "grantee" seem kind of terrible, and a generic like "Target" isn't really less overloaded than "Object".

This revision is now accepted and ready to land.Sep 26 2016, 1:49 PM
This revision was automatically updated to reflect the committed changes.