Conversation
@fabricio-aguiar to confirm, this will only occur in dev installs right? |
yes, all my changes were on pulp-file:
binding: pulp-file-client
source_dir: "/home/vagrant/devel/pulp_file" |
@fabricio-aguiar can you open a pulplift PR I can test with this also? |
I can do it, but if you have a |
I will test using the example.dev-config.yml |
|
Thanks! I'm testing it now. |
pulp_file worked for me!
|
Do these installations come from PyPI in some cases? I think we want them to be from source installs in all cases. |
roles/pulp-devel/handlers/main.yml
Outdated
@@ -0,0 +1,6 @@ | |||
--- | |||
- name: Install pulpcore binding package via PyPI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs to be built from local source
roles/pulp-devel/tasks/main.yml
Outdated
with_dict: "{{ pulp_install_plugins }}" | ||
when: item.value.binding is defined | ||
notify: | ||
- Install pulpcore binding package via PyPI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs to be done via local source
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without pulpcore binding, any plugin binding would be useless, because tests need pulpcore binding also
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I just imagined it would come from a local checkout of pulpcore. Perhaps I'm thinking that is normal because I'm usually working on pulpcore and need the source install there, but other devs maybe don't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my idea with this is to assure the dev will have the env ready for running functional tests as soon it is provisioned, that is how I understood: https://pulp.plan.io/issues/6032#note-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I imagined it pbindings would be called late in the dev setup process. That would be better I think because then the bindings version received matches the version of pulpcore they are actually running. It also would be simpler because you can just let pbindings do it all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I saw late in the process I mean after Pulp is running because it needs to provide the openAPI schema
fi | ||
|
||
./generate.sh $@ | ||
pip install ./$1-client |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually does use the local source, so this part is good.
@@ -144,3 +144,32 @@ pyclean () { | |||
find . -type d -name "__pycache__" -delete | |||
} | |||
_pyclean_help="Cleanup extra python files" | |||
|
|||
pbindings(){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does making some way to install
, uninstall
, or reinstall
make any sense. As code changes in PRs it would be convenient to have 1 command to reinstall that plugins' bindings. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the command is idempotent, so for reinstall, you just need to call it again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh nice that makes it simple which is great. No changes needed here.
I tested this and it worked well for me. The vagrant up worked, and also |
It's hard to tell the bindings are not coming from PyPI with |
from PyPI it has version number, building locally the version is 0.0.0 |
https://pulp.plan.io/issues/6032
closes #6032
How to use:
pbindings pulp_file python
it will install pulpcore and pulp_file python bindings