Validate secrets routes on the backend
Problem to solve
From 5.
in the Vue Router section of our Vue guide:
Optional. To also allow using the path helper for child routes, add controller and action parameters to use the parent controller.
resources :iteration_cadences, path: 'cadences(/*vueroute)', action: :index do resources :iterations, only: [:index, :new, :edit, :show], constraints: { id: /\d+/ }, controller: :iteration_cadences, action: :index end
This means routes like /cadences/123/iterations/456/edit can be validated on the backend, for example to check group or project membership. It also means we can use the _path helper, which means we can load the page in feature specs without manually building the *vueroute part of the path.
Proposal
Once we're getting real secrets data from the backend, we should implement this for secrets so that routes like /-/secrets/some_secret_key/edit
can be validated on the backend.
Edited by Miranda Fluharty