Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[POC] Decoupling config from Pylons #2843

Closed
wants to merge 20 commits into from
Closed

Conversation

amercader
Copy link
Member

See #2842

rossjones and others added 16 commits September 4, 2015 15:33
Currently routes /api/4/* to a Flask controller which will then:

1. Only process GET requests
2. Not handle auth at all.

Will require the DispatcherMiddleware be replaced to hand
requests to Flask based on the paths that the Flask app says
it can handle.  Flask though will then be given a partial path
and so the request path will need reconstituting.
Unfortunately we need to check the path for the request against a known
list of partial paths that Flask knows about - and then we route those
requests to Flask.
Flask won't let you jsonify lists, so we'll just do it ourselves
Taking the old CKAN code for identifying the user doesn't yet seem
to work, I've ruled out the c object being the problem (i.e. I can
manually set it) but Repoze doesn't appear to be setting REMOTE_USER
in the environment, and so it isn't being used.
We need to make sure ther flask app is passed through the same
middleware stack that the Pylons app is ...
Conflicts:
	requirements.txt
This is meant to be used in the ckan context. It will internally proxy
to the Pylons and Flask configs
Instead of importing directly from Pylons, import from ckan.common
If we really need to access the Pylons config object, then we can access
it via config.pylons_config.
All these should be refactored anyway to use helpers.FunctionalTestBase
@amercader
Copy link
Member Author

Closed in favour of #3163

@amercader amercader closed this Jul 13, 2016
@amercader amercader deleted the poc-abstract-config branch July 13, 2016 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants