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

Cavatica API endpoint is hardcoded in main.py #1

Closed
groverj3 opened this issue Sep 28, 2021 · 3 comments · Fixed by #2
Closed

Cavatica API endpoint is hardcoded in main.py #1

groverj3 opened this issue Sep 28, 2021 · 3 comments · Fixed by #2

Comments

@groverj3
Copy link

Hi there,

Thanks for making this! I was intending on making one, myself, but found yours. No need to reinvent the wheel :). I tested this action, and found that the API endpoint for Cavatica is hardcoded. I understand that INCLUDE uses that platform. However, there isn't anything stopping this from being broadly useful if the API endpoint can be passed from the .yml like app_name, workflow_path, auth_token, etc.

@thomasyu888
Copy link
Collaborator

Thanks for noting that. I shall make that change next week after I get back in the office.

@thomasyu888
Copy link
Collaborator

@groverj3. This is supported in version v0.0.2

@groverj3
Copy link
Author

groverj3 commented Oct 6, 2021

Thanks, @thomasyu888. Tested this yesterday and it's working nicely. I've put together an example of using it to push to the CGC here.

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 a pull request may close this issue.

2 participants