-
Notifications
You must be signed in to change notification settings - Fork 81
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
standalone config - change pulp api path to '/api/automation-hub/pulp/api/v3/' (dev) or '/api/galaxy/pulp/api/v3/' (prod) #2135
Conversation
…pulp/api/v3/' ansible/galaxy_ng#1247 was merged, so task won't work in dev ui without this No-Issue (but related to AAH-1544)
09402ab
to
8f98b32
Compare
Before second commit (and also everywhere on master now):
After second commit:
(Third ✔️ :)) .. yeah, I think we can definitely say that prod needs This may also cause issues with downstream builds though, but that's for a separate MR. |
Merging to fix tests on master |
@himdel the pulp api moved for all deployment modes, so for standlone the UI will need to access it in it's new location. We also plan to add a redirect for standalone. |
related to packaging!11, ansible#2135 mostly undoes ansible#1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/)
related to packaging!11, ansible#2135 mostly undoes ansible#1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/) No-Issue
related to packaging!11, ansible#2135 mostly undoes ansible#1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/) No-Issue
related to packaging!11, ansible#2135 mostly undoes ansible#1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/) No-Issue
related to packaging!11, ansible#2135 mostly undoes ansible#1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/) No-Issue
…2501) * PULP_API_BASE_PATH - hardcode to use API_BASE_PATH + 'pulp/api/v3/' related to packaging!11, #2135 mostly undoes #1857 config changes but not code changes `packaging/roles/publish/files/config/downstream.webpack.config.js` can't easily have version-dependent logic, so having individual webpack configs provide `PULP_API_BASE_PATH` doesn't quite work, but having the constant available in code is still useful. => ignoring any PULP_API_BASE_PATH config options or env variables, hardcoding PULP_API_BASE_PATH global to be based on API_BASE_PATH in 4.6+ (for 4.5 and older, the url is just /pulp/api/v3/) No-Issue * test/: consistently use pulpPrefix for PULP_API_BASE_PATH
ansible/galaxy_ng#1247 was merged, so tasks won't work in dev ui without this
Cc @awcrosby .. do you know what happens for standalone prod? Should we change the pulp apis to
/api/galaxy/pulp/api/v3/
or do they stay in the original place?