Unanswered
Hi Steve Hushek,
-
you need to request the Q2 team on the q2 developer portal to create a project under your stack .Q2 creates a repo .and you can switch to the repo in your stack. or else you can clone the project from the git and you need to activate the project env(source .env/bin/activate). you can copy the existing .env folder from the SDK folder in your stack before activating.
-
you need to create a entry point extension using the Q2 command q2 create_entrypoint and you can run the installed entry point using command q2 entry point name
-
it's better to have the latest SDK .so before installing the extension you can upgrade SDK to the latest.
Thanks,
Swarup
61 Views
0
Answers
4 years ago
4 years ago
For those curious and looking to figure out what happened to fix this in the future. Steve's user was missing some commands in his bash profile. This caused his environment not to activate and set the env variables.
— Trey Teter 4 years agoOnce that was fixed, there was a bug in the old sdk version he was on that caused the scripts to not work. After updating to a more recent version, everything worked as intended.
— Trey Teter 4 years agoIf someone runs into an issue like this in the future, creating a support ticket is fine. You could manually activate like Swarup was suggesting and set all your environment variables manually, but this is why we typically set this all ahead of time.
— Trey Teter 4 years ago