You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first thing I noticed was if there are errors running OctoDNS a comment is still left on the pr. I don't think this is really an issue, it's just not what I expected since OctoDNS didn't successfully run. I figured this step would throw an error and the workflow would end here. My initial run had the wrong api credentials which resulted in the following log output:
Traceback (most recent call last):
File "/usr/local/bin/octodns-sync", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.7/site-packages/octodns/cmds/sync.py", line 37, in main
manager = Manager(args.config_file)
File "/usr/local/lib/python3.7/site-packages/octodns/manager.py", line 118, in __init__
self.providers[provider_name] = _class(provider_name, **kwargs)
File "/usr/local/lib/python3.7/site-packages/octodns/provider/rackspace.py", line 64, in __init__
auth_token, dns_endpoint = self._get_auth_token(username, api_key)
File "/usr/local/lib/python3.7/site-packages/octodns/provider/rackspace.py", line 85, in _get_auth_token
x['name'] == 'cloudDNS'][0]['endpoints'][0]['publicURL']
IndexError: list index out of range
And this is the comment that was left:
Expected Behavior
I figured this step would throw an error and the workflow would end here.
Actual Behavior
if there are errors running OctoDNS a comment is still left on the pr.
Possible Fix
I figured this step would throw an error and the workflow would end here.
Steps to Reproduce
Enable and configure this action
Enable and configure add_pr_comment
Run octodns-sync with invalid credentials
Context
I don't think this is really an issue, it's just not what I expected since OctoDNS didn't successfully run.
Your Environment
Version used: main
Link to your project:
The text was updated successfully, but these errors were encountered:
octodns-sync returns non-zero when it fails, and script -e returns the correct code. entrypoint.sh just doesn't respond to it. I think this should be straightforward, will set up a fix to test.
Description
From #35 (comment) :
Expected Behavior
Actual Behavior
Possible Fix
Steps to Reproduce
add_pr_comment
Context
Your Environment
The text was updated successfully, but these errors were encountered: