Repository navigation
Update atlas fp - #359
Merged
Merged
Update atlas fp#359
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates ATLAS FP to handle their callback URL functionality by using my fork of the tom_base repo.
@nvieira-astro Please just verify that the ATLAS FP works the same as before. We can't test the callback URL until it is deployed and there is a public https url for ATLAS to contact. I've developed the code to behave as before unless a variable is set in the django settings.
Note the updates to requirements.txt which use custom branches/forks of candidate_vetting and tom_base that required for this to work.